-
Notifications
You must be signed in to change notification settings - Fork 1.1k
CI failures: Cannot run program "./cs": error=2, No such file or directory #17119
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
Comments
I wonder if it is a problematic CI worker. |
The workers appear to be all online. Why do you think this has to do with a worker? |
I was just a theory based on how often the issue happened. I also noticed that this issue happens more often when the CI is at full capacity (i.e. in the CET afternoons). |
Here is anotherone from today https://github.com/lampepfl/dotty/actions/runs/4430193399/jobs/7771618203?pr=17114 |
This should provide more insight on why scala#17119 happens.
I suspect this could be because the test fails to download coursier at some times. The way it is currently written, there is no safeguard against a failure in download.
I've added a PR #17127 that safeguards against failed downloads and mimics the intent of |
Now we got a different error
https://github.com/lampepfl/dotty/actions/runs/4487258054/jobs/7890504165?pr=17059 |
Yes, I suspect this is a problem with git.io reliability. Can we switch it using github.com instead?
|
git.io is a URL shortener which, it seems, is unreliable.
git.io is a URL shortener which, it seems, is unreliable.
This should provide more insight on why scala#17119 happens.
git.io is a URL shortener which, it seems, is unreliable.
This should provide more insight on why #17119 happens.
This should provide more insight on why scala#17119 happens.
This should provide more insight on why scala#17119 happens.
We have a few spurious failures of CI involving
CoursierScalaTests
. Usually rerunning the tests fixes the issue.The text was updated successfully, but these errors were encountered: