-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Invalid memory access in test_alpine #10366
Invalid memory access in test_alpine #10366
Comments
You mean locally as in local docker or local alpine? I think it's started to fail more often with the update to alpine:3.13. But it doesn't make much sense either. We could try to run alpine test with verbose for a while to see if it's always in the same spec. |
I ran compiler_spec locally in the alpine build container. And it reproduced similar, but not exactly the same spec. As far as I can see, in CI it always breaks in the third spec or not at all. So verbose output wouldn't be necessary to track that. |
The alpine images based on 3.13 have some issues. The maintenance_release is unable to succeed and also the test_alpine. I've verified that locally, it fails in the So for now I am reverting the alpine images to 3.12 as published at crystal-lang/distribution-scripts@80c83b2 . But I am leaving the 3.13 alpine images just in case The related docker images are:
Ref from crystal-lang/distribution-scripts#83:
|
The
test_alpine
job is broken on master. Example of a broken build: https://github.com/crystal-lang/crystal/runs/1818349096The earliest broken nightly build is 33c97d4. So it would seem that the relevant change was introduced between that and dc0a32f. However, PR builds before that already show the same error, for example in 77f7f02
But the following nightly was okay, so the error doesn't reproduce consistently. In CI it appears always very early on in compiler specs after the first couple of examples. But locally I've seen it occur later on after a few dozend examples.
The text was updated successfully, but these errors were encountered: