-
Notifications
You must be signed in to change notification settings - Fork 3
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
GHA failures in aiidalab-launch #163
Comments
Maybe duplicate of #154, see discussion there. |
thanks for reporting this @danielhollas. When #154 happened, it is stuck in the command line rather than printing an error message and exiting so you can type new on the terminal, correct? |
It is stuck and I needed to the Ctrl+C and only then the error was printed. |
I see, I'll take a look at #154. The error seems like the async function is called from another coroutine directly without |
Yeah. Just note from the discussion there that Simon already spent some time on it and couldn't figure it out, so it might be a pain, maybe not the biggest priority now, although it is annoying. btw: Could you make a release of |
Sure, I'll make the release. Thanks a lot for the fixes! |
In failures here and here),the test suite no longer times out, but actually fails in a reasonable amount of time. The failures are too generic to pinpoint the issue, since it says the container fails to start. Probably more debug logging is needed to debug this, we need the pytest to somehow print the container logs when it fails to start. |
Tests seem to be timing out randomly on GHA (e.g. after 30 minutes).
Interestingly, the pytest tests seem to always finish fine, but then the workflow step gets stuck? Very strange...
See for example
https://github.com/aiidalab/aiidalab-launch/actions/runs/3550589631/jobs/5972824480
The text was updated successfully, but these errors were encountered: