-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Should we improve cell toolbar logic or disable cell toolbar in tests? #15305
Comments
Also, there is #15314 which might help with things. |
It continues to be a drag on maintenance and development (for example see incorrect snapshot update of |
In discussion on #15422 with @brichet we note that after refreshing the page the toolbar often does not hide even though it should. I can reliably reproduce this on This looks like a bug in the logic which has implications on the maintainers ability to move forward because these tests are always flaky and often fail the run, adding about 15 to 30 minutes wasted to each PR review (we need to download the artifact, unpack, analyze, re-run a few times). |
This is also a hurdle for new contributors as seen in #16284. |
Description
A bottleneck in the PR review are often the visual test failures. In addition to a few existing test cases which are flaky, a very common problem is the cell toolbar randomly showing up when it should not or randomly hiding when it should be visible for a split second. It is not a problem in normal usage when it is mostly unnoticeable, but it leads to many spurious failed tests, wasting hundreds of hours in CI time and in the time of maintainers, for example:
Reproduce
Screenshots taken from https://github.com/jupyterlab/jupyterlab/actions/runs/6640451043/job/18051878571?pr=15296 but every other PR has this issue. If you seen green status it likely means that one of the maintainers manually restarted the job after checking the failures manually (so they did that instead of improving the codebase or merging a PR).
The text was updated successfully, but these errors were encountered: