-
Notifications
You must be signed in to change notification settings - Fork 8.5k
SO Tagging: fix flaky test and re-enable it #82930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pgayvallet
merged 11 commits into
elastic:master
from
pgayvallet:kbn-82556-fix-sot-vis-flacky-ftr-1
Nov 18, 2020
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
d216b9e
fix flaky test and re-enable it
pgayvallet c2d1238
wait for table to load before to perform operations
pgayvallet 374814f
Merge remote-tracking branch 'upstream/master' into kbn-82556-fix-sot…
pgayvallet db86c3b
move everything out of ciGroup2 for flaky test runner
pgayvallet 46da2af
add debug block for flaky runner
pgayvallet 2909b19
use correct vis name
pgayvallet d37a5b7
Merge remote-tracking branch 'upstream/master' into kbn-82556-fix-sot…
pgayvallet c77f036
remove test sync
pgayvallet 5e9a93c
Revert "move everything out of ciGroup2 for flaky test runner"
pgayvallet 5861e50
Merge remote-tracking branch 'upstream/master' into kbn-82556-fix-sot…
pgayvallet 61980e9
Merge remote-tracking branch 'upstream/master' into kbn-82556-fix-sot…
pgayvallet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: There could be a lot of reasons for waiting for a DOM element to be rendered. What if we increase
timeoutinselectFilterTagsmethod instead?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBH after 100 runs against my local I couldn't reproduce the flaky failure even once. The failure message indicates that for some reason, 1. the tag filter was not applied (
Visualization 2 (tag-2)is present in the table) and 2. the new vis was not created (My new markdown vizis not), and I don't really how we could come as far as the last assertion in that state without failing before in the test. So I kinda did the best I could with additional synchronizations / waiting steps to see if that would resolves it on CI (renamed the PR accordingly).I can do what you suggest though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pgayvallet Have you tried to leverage https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/build
to run a flaky test on CI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not. Can this be ran against a PR branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can configure it

Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First run had a failure on another test - https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/978/testReport/junit/X-Pack%20Saved%20Object%20Tagging%20Functional%20Tests/x-pack_test_saved_object_tagging_functional_tests_dashboard_integration%C2%B7ts/Kibana_Pipeline___agent_2___saved_objects_tagging___functional_tests_dashboard_integration_creating_allows_to_create_a_tag_from_the_tag_selector/
but the error message was a little more explicit on that one. trying something else by waiting for the table to load