Small clean up with visualize test + extra debug log

[stacey-gammon]

Investigate and fix #13754

[stacey-gammon]

First run passed the test in question, though failed at the end due to an s3 upload error. So for our intents, it counts as a pass:

 debg  isGlobalLoadingIndicatorVisible
13:49:31 01:49:31.829          │ debg  TestSubjects.exists(globalLoadingIndicator)
13:49:31 01:49:31.829          │ debg  existsByDisplayedByCssSelector [data-test-subj~="globalLoadingIndicator"]
13:49:31 01:49:31.901          │ debg  isGlobalLoadingIndicatorHidden
13:49:31 01:49:31.902          │ debg  findByCssSelector [data-test-subj="globalLoadingIndicator"].ng-hide
13:49:32 01:49:32.087          │ debg  in displayedByCssSelector: kbn-truncated.toast-message.ng-isolate-scope
13:49:32 01:49:32.160          │ debg  getToastMessage: Visualization Editor: Saved Visualization "visualization from add new link"
13:49:32 01:49:32.160          │ debg  clickToastOK
13:49:32 01:49:32.884          │ debg  in findAllByCssSelector: li.gs-w
13:49:33 01:49:33.405          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.410          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.414          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.420          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.425          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.430          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.435          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:33 01:49:33.439          │ debg  Find.childDisplayedByCssSelector: [data-test-subj~="dashboardPanelTitle"]
13:49:34 01:49:34.040          │ info  visualization titles = Visualization PieChart,Visualization☺ VerticalBarChart,Visualization漢字 AreaChart,Visualization☺漢字 DataTable,Visualization漢字 LineChart,Visualization TileMap,Visualization MetricChart,visualization from add new link
13:49:34 01:49:34.041          │ debg  Taking screenshot "/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/test/functional/screenshots/session/Dashboard-visualization-sizes.png"
13:49:34 01:49:34.042          └- ✓ pass 

Not that I did anything to actually fix it, but am curious to see how the output looks during a failure and how flaky this test is.

Jenkins, test this.

[stacey-gammon]

Second time passed.

Jenkins, test this.

[stacey-gammon]

Passed a third time.

cc @timroes -- any idea how often I should be seeing this error? I doubt my slight changes fixed it. I could perhaps check this in since it's just a small clean up, and then the next time we'll run into it I'll at least have a little extra debug out.

Jenkins test this.

[stacey-gammon]

another failure for s3, but a pass for the add new visualization link test.

jenkins, test this

[stacey-gammon]

Unit test failures this time:

18:44:36 Chrome 59.0.3071 (Linux 0.0.0): Executed 869 of 872 SUCCESS (0 secs / 3.595 secs)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0)  "before each" hook FAILED
18:44:36 	Error: Uncaught TypeError: Cannot read property 'key' of undefined (http://localhost:5610/bundles/tests.bundle.js?shards=4&shard_num=1:99966)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0): Executed 870 of 872 (1 FAILED) (0 secs / 3.595 secs)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0): Executed 871 of 872 (1 FAILED) (0 secs / 3.606 secs)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0)  "after each" hook FAILED
18:44:36 	TypeError: Cannot read property '$injector' of null
18:44:36 	    at Context.<anonymous> (http://localhost:5610/bundles/tests.bundle.js?shards=4&shard_num=1:101948:32)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0): Executed 872 of 872 (2 FAILED) (0 secs / 3.615 secs)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0)  "after each" hook FAILED
18:44:36 	TypeError: Cannot read property '$injector' of null
18:44:36 	    at Context.<anonymous> (http://localhost:5610/bundles/tests.bundle.js?shards=4&shard_num=1:101948:32)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0): Executed 873 of 872 (3 FAILED) (0 secs / 3.615 secs)
18:44:36 Chrome 59.0.3071 (Linux 0.0.0): Executed 873 of 872 (3 FAILED) (28.513 secs / 3.615 secs)
18:44:36 Warning: Task "karma:ciShard-1" failed.� Use --force to continue.
18:44:36 
18:44:36 Aborted due to warnings.

Not much information as to where they are coming from. Though not the test I am investigating.

This last run is a no-op. Will sync with master to see if I need some changes.

[stacey-gammon]

Passed 5 times. Lets get this checked in and if any more errors occur I'll take another look. There were two toast message statements in a row and I wanted to see which one was failing. Hopefully the added debug line will help when it hits again.

To be clear, I don't believe I fixed the bug, but perhaps changing the code slightly altered the timing and made it hard to reproduce.