-
Notifications
You must be signed in to change notification settings - Fork 162
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
CI: The Job LPython CI / Check Release build (pull_request) seems flaky #2162
Comments
Can you describe the exact issue? or point to failure? Rarely, it fails because of some issues on the GH actions side. |
I updated the description of this issue. |
The job Check Release build passed in the third run attempt. Something does not seem right. I will explore more about this. |
The failure seems different though:
and
and (3x):
But all three failures seem to be caused by the lpython compiler executing some illegal instruction. That typically happens with the Release mode is compiled to a newer architecture than it runs, quite common at a CI. I think we just need to lower the optimization options, perhaps keep |
I think the original failure is
This was previously not being caught because bash would not fail even if there was a failure. Therefore, the CI was failing at a later point when running reference tests. Since #2194, the above |
The release build seems to fail too often. I request review of #2212 at the earliest convenience. If in case it does not fix the issue, we can try/find other approaches. |
This issues seems to be fixed. It does not seem to be flaky now. |
It seems to falsely fail for me on first run. It seems to pass on second run attempt.
False Failures:
The text was updated successfully, but these errors were encountered: