-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Flaky UI tests #7370
Flaky UI tests #7370
Comments
Thanks @jtpio for the ping. Wondering if this is only a matter of time for the button to be visible, and if we want to fix it (if it's inconvenient to use) or only fix the test (waiting for the button to be visible). |
Usually not, so it might indeed just be an issue with the tests. There is some logic to wait for the kernel status animations to be gone before taking the screenshot, which may not be enough: notebook/ui-tests/test/mobile.spec.ts Lines 58 to 59 in 08fe5c5
But maybe there could indeed also be a check to wait for that button to be visible, just to be sure. |
I can take a look at the test and we'll see if it's enough. |
Re-opening to keep track of updating to a new JupyterLab version, and check if it fixes the flakiness. |
From #7378 (which should include jupyterlab/jupyterlab#16335), it looks like this time it is the button to toggle the virtual scrollbar that is sometimes showing up:
|
I think it is another computation issue with the toolbar, but I can't tell why it was not an issue before. |
Opened jupyterlab/jupyterlab#16409, it fixes this issue locally, during tests and usage. |
I hope there will not be other issues with the new change... 😄 |
Yes, thanks for looking into them! I'll re-open to keep track of it, which should be fixed after the next JupyterLab update. |
Closing as likely fixed by #7416. We can re-open if the failure still happens in the future. Thanks! |
It looks like we still have some flakiness with the notebook toolbar sometimes missing the overflow button menu:
cc @brichet who looked into the notebook toolbar recently (as part of #7311) and may know if that might also be happening in JupyterLab.
Originally posted by @jtpio in #7361 (comment)
The text was updated successfully, but these errors were encountered: