Bring back most of the filtering tests, only bypass the known current issues#22787
Conversation
💔 Build Failed |
💔 Build Failed |
|
unrelated failure:
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 |
💔 Build Failed |
|
Same error: jenkins, test this |
💔 Build Failed |
9561362 to
74b18a3
Compare
💔 Build Failed |
|
failed on jenkins, test this |
💔 Build Failed |
74b18a3 to
3964316
Compare
💔 Build Failed |
|
another issue with the dashboard snapshot test not finding the save dashboard success toast. jenkins, test this |
💔 Build Failed |
|
Failed on snapshot tests for a different reason, the comparison failed: |
3964316 to
4b97728
Compare
💚 Build Succeeded |
|
so weird. Well, lets just see if we can get these changes in, when run only once. jenkins, test this |
💚 Build Succeeded |
|
retest |
There was a problem hiding this comment.
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).
ppisljar
left a comment
There was a problem hiding this comment.
not sure why number of pie slices changed, apart from that LGTM, lets run the tests few more times to be sure its stable.
💔 Build Failed |
|
Failed on jenkins, test this |
💚 Build Succeeded |
|
retest |
💚 Build Succeeded |
|
retest |
💔 Build Failed |
|
failed on: will retest again after rebasing |
4b97728 to
c5751e0
Compare
💚 Build Succeeded |
|
retest |
💚 Build Succeeded |
|
K, I'm merging. No filter failures, just other sporadic unrelated failures. |
… 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
Bring back most of the filtering tests.
Note:
There is something really weird going on when the
_dashboard_filteringtest suite is run multiple times, another error is consistently hit in the_dashboard_snapshotsuite.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.