-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Multi-user feature UI integration tests are unstable. #377
Comments
…Actions creates the new coverage workflow.
Unfortunately the test is now failing either more often or every time, so the attempt to fix it needs more work.
|
As it is causing test failures for other commits/PRs.
Update: the "Add ROA" test does fail but not every time. |
Interestingly the same test suite sometimes fails a different way in one of the other tests:
|
I'm now aware of at least four test failures that are sometimes occuring:
I can't yet reproduce these locally, presumably because my development machine is faster than the GitHub Actions runner VMs and so the state is as expected rather than not yet having reached the required state. *1: According to this we should configure cypress to ignore this error. For more information see this as well. Example JS Cypress code that shows how to catch uncaught exceptions can be seen here. |
…GH Action runner VMs before Krill is able to validate it. (#377)
…ceeded" errors using a custom Cypress uncaught exception handler. Unable to reproduce locally or even confirm that the new handler is being invoked. (#377)
…ceeded" errors using a custom Cypress uncaught exception handler. Unable to reproduce locally or even confirm that the new handler is being invoked. (file missed from previous commit) (#377)
* Use a less short 'short-lived' token that doesn't expire in the GH Action runner VMs before Krill is able to validate it. (#377) * Attempt to suppress occasional spurious "ResizeObserver loop limit exceeded" errors using a custom Cypress uncaught exception handler. Unable to reproduce locally or even confirm that the new handler is being invoked. (#377)
Can I reproduce the unstable tests on a self-hosted runner? (#377)
Can I reproduce the unstable tests on a self-hosted runner? (#377)
Update: There have been very few (none?) failures since the ResizeObserver workaround was tuned and the "Add ROAs" test was disabled. The "Add ROAs" test still needs work to make it deterministic however. |
…a master branch commit 30215b85. (#377).
Closing as the UI tests in the dev branch have been stable for a week now. Will re-open if another failure occurs. |
Note: This relates to the
multi-user
feature in thev0.8.1-bis
branch.The test in
multi_user_config_file_with_ta.js
sometimes fails with:I suspect that the test needs to wait for Krill to issue the resources and for them to appear in the UI.
The text was updated successfully, but these errors were encountered: