-
Notifications
You must be signed in to change notification settings - Fork 323
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
Random GUI Check CI failures. #11458
Comments
Not sure on which list to put it, but I've been getting some failures during Packaging: https://github.com/enso-org/enso/actions/runs/11611460774/job/32336224968?pr=11455#step:8:166
It did not contain a playwright test report
|
https://github.com/enso-org/enso/actions/runs/11598732906/job/32296813889?pr=11417
|
The two comments above are the same issue, which I don't want to be part of this task, because this is an integration test: so it may be as well an engine issue :) This time we don't receive update for a type in time (there's 5 second timeout I think). I may bump the timeout, the question is what do we call an "acceptable" waiting time for the user :) |
not sure if this one is just caused by insufficient timeouts.
|
Part of #11458 Should get rid of the "magical" CI failure: https://github.com/enso-org/enso/actions/runs/11576387008/job/32225209090#step:7:254
timeouts would not avail us, it looks like some driver crash: https://github.com/enso-org/enso/actions/runs/11681103703/job/32534992167#step:7:1102
|
Note to anyone adding entries here: Please remember to download the report and upload it here before re-running your failed action, because re-running erases old artifacts.
Dashboard
Project View
Deeply Magical ✨
The text was updated successfully, but these errors were encountered: