Skip to content

Bring back most of the filtering tests, only bypass the known current issues#22787

Merged
stacey-gammon merged 3 commits intoelastic:masterfrom
stacey-gammon:2018-09-06-only-skip-known-issues
Sep 13, 2018
Merged

Bring back most of the filtering tests, only bypass the known current issues#22787
stacey-gammon merged 3 commits intoelastic:masterfrom
stacey-gammon:2018-09-06-only-skip-known-issues

Conversation

@stacey-gammon
Copy link
Copy Markdown

@stacey-gammon stacey-gammon commented Sep 6, 2018

Bring back most of the filtering tests.

Note:
There is something really weird going on when the _dashboard_filtering test suite is run multiple times, another error is consistently hit in the _dashboard_snapshot suite.

Rather than tackle that weird issue here, I'm just going to work on getting the filtering tests back on so no more bugs sneak by, and can then investigate the other issue separately.

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

stacey-gammon commented Sep 7, 2018

unrelated failure:

Error: Expected to find "saveDashboardSuccess" toast after saving dashboard
    at DashboardPage.saveDashboard (test/functional/page_objects/dashboard_page.js:316:15)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
      

I think I will have a fix for this one here: #22766

Hm, no, not sure what is going on with that failure. The screenshot shows that there is no toast but looks like the dashboard was saved (at least it's not in edit mode).... maybe it took so long to save that the toast disappeared?

jenkins, test this

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

Same error: Error: Expected to find "saveDashboardSuccess" toast after saving dashboard. Having this PR be the culprit does not really make sense to me, based on the changes. 😕

jenkins, test this

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon stacey-gammon force-pushed the 2018-09-06-only-skip-known-issues branch from 9561362 to 74b18a3 Compare September 7, 2018 19:13
@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

failed on UI Functional Tests.test/functional/apps/context/_filters·js.context app context filters should be toggleable via the filter bar

jenkins, test this

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon stacey-gammon force-pushed the 2018-09-06-only-skip-known-issues branch from 74b18a3 to 3964316 Compare September 10, 2018 14:10
@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

another issue with the dashboard snapshot test not finding the save dashboard success toast.

jenkins, test this

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

Failed on snapshot tests for a different reason, the comparison failed: /_dashboard_snapshots·js.dashboard app using current data dashboard snapshots compare area chart snapshot

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@stacey-gammon
Copy link
Copy Markdown
Author

so weird. Well, lets just see if we can get these changes in, when run only once.

jenkins, test this

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@stacey-gammon
Copy link
Copy Markdown
Author

retest

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why has this changed ?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because I added a test to remove the saved filter above. I did this as clean up, so the test suite leaves the code just as it was when it started. I wanted to run the suite muiltiple times in a row and If I didn't do this, it'd fail the second time around because the filter is then actually saved on the instance (good or bad, I'm not reloading all the index data after each test suite to save time).

Copy link
Copy Markdown
Contributor

@ppisljar ppisljar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure why number of pie slices changed, apart from that LGTM, lets run the tests few more times to be sure its stable.

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

Failed on UI Functional Tests.test/functional/apps/context/_filters·js.context app context filters should be toggleable via the filter bar

jenkins, test this

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@stacey-gammon
Copy link
Copy Markdown
Author

retest

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@stacey-gammon
Copy link
Copy Markdown
Author

retest

@elasticmachine
Copy link
Copy Markdown
Contributor

💔 Build Failed

@stacey-gammon
Copy link
Copy Markdown
Author

failed on:

20:32:28    │ERROR [POST http://localhost:9515/session / {"desiredCapabilities":{},"requiredCapabilities":{}}] unknown error: Chrome failed to start: exited abnormally
20:32:28    │        (unknown error: DevToolsActivePort file doesn't exist)
20:32:28    │        (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
20:32:28    │        (Driver info: chromedriver=2.41.578700 (2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 4.9.0-8-amd64 x86_64)
20:32:28    │          at Server._post (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/kibana/test/functional/services/remote/verbose_remote_logging.js:34:21)
20:32:28    │          at Server.createSession (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/kibana/node_modules/leadfoot/Server.js:362:15)
20:32:28    │          at attemptToCreateCommand (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/kibana/test/functional/services/remote/leadfoot_command.js:38:32)
20:32:28    │          at Promise.race (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/kibana/test/functional/services/remote/leadfoot_command.js:86:11)
20:32:28    │          at initLeadfootCommand (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/kibana/test/functional/services/remote/leadfoot_command.js:63:5)
20:32:28    │          at RemoteProvider (/var/lib/jenkins/workspace/elastic+kibana+pull-request+multijob-selenium/kibana/test/functional/services/remote/remote.js:40:29)
20:32:28    │          at <anonymous>
20:32:28    │ warn 1 processes left running, stop them with procs.stop(name): [ 'kibana' ]
20:32:29    │ info [kibana] exited with 0 after a minute
20:32:29 
20:32:29 Failure initializing 1 service(s)

will retest again after rebasing

@stacey-gammon stacey-gammon force-pushed the 2018-09-06-only-skip-known-issues branch from 4b97728 to c5751e0 Compare September 13, 2018 11:27
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@stacey-gammon
Copy link
Copy Markdown
Author

retest

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

@stacey-gammon
Copy link
Copy Markdown
Author

K, I'm merging. No filter failures, just other sporadic unrelated failures.

@stacey-gammon stacey-gammon merged commit 5e44e00 into elastic:master Sep 13, 2018
stacey-gammon pushed a commit to stacey-gammon/kibana that referenced this pull request Sep 13, 2018
… issues (elastic#22787)

* Bring back most of the filtering tests, only bypass the known current issues.

* Clean up after the test suite run so it can be run multiple times in a row.

* goal and guage issues were because of a bad cache
stacey-gammon pushed a commit that referenced this pull request Sep 13, 2018
… issues (#22787) (#22996)

* Bring back most of the filtering tests, only bypass the known current issues.

* Clean up after the test suite run so it can be run multiple times in a row.

* goal and guage issues were because of a bad cache
@liza-mae liza-mae added failed-test A test failure on a tracked branch, potentially flaky-test and removed flaky-failing-test labels Nov 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

failed-test A test failure on a tracked branch, potentially flaky-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants