-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Make visualization.waitForRender more generic #21342
Make visualization.waitForRender more generic #21342
Conversation
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
b3ca2c7
to
79c561f
Compare
💔 Build Failed |
79c561f
to
579c2dd
Compare
💔 Build Failed |
💔 Build Failed |
Finally failed where I wanted it to fail: Now to uncomment the |
2aec48c
to
bc00c7f
Compare
💔 Build Failed |
Failed because in the filtering test a visualization is saved with a different name, which makes running the same test multiple times in a row fail. |
💔 Build Failed |
💔 Build Failed |
c88cae4
to
fda9a4e
Compare
💔 Build Failed |
fda9a4e
to
55de839
Compare
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
Hm, failed on:
Didn't change any real code logic so this shouldn't have introduced a bug... Will try locally. Ah, this is flaky (#21642): jenkins, test this |
retest |
💔 Build Failed |
Hit #21642 again jenkins, test this |
… verify that flakiness is gone
This should be fixed but for now I'd like to continue testing the rendering test refactor. The issue is that this _dashboard_filtering test modifies saved objects. The "using current data" tests do not reset the data after each suite run to try to cut back on the time tests take. With all the work infra is doing we can probably remove this little attempt at a clean up. For now though, stay focused on the task...
b2bdc2e
to
a6cab91
Compare
💔 Build Failed |
💚 Build Succeeded |
retest |
💚 Build Succeeded |
closing in favor of #21688 |
No description provided.