-
Notifications
You must be signed in to change notification settings - Fork 16
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
[ocaml5-issue] Bytecode segfaults on Ephemeron test #181
Comments
The CI just hit another
For future reference I include a copy of the relevant CI log for the above
|
Two native code https://github.com/jmid/multicoretests/actions/runs/3461648589/jobs/5779520524
and https://github.com/jmid/multicoretests/actions/runs/3461587444/jobs/5779384555
|
I just checked that the 3 native runs you mention were using an old OCaml compiler. https://github.com/jmid/multicoretests/actions/runs/3461587444/jobs/5779384555#step:4:457 says: The bytecode run, on the other hand, says: |
Good detective work, sir! 👍 |
The native mode We are still seeing them on On the #195 merge CI run: https://github.com/jmid/multicoretests/actions/runs/3477572101/jobs/5813892424
On a CI run from PR #197: https://github.com/jmid/multicoretests/actions/runs/3478421458/jobs/5815768968
|
Maybe you could revert your change of title then ;-) |
Just when we thought this was bytecode only, ... CI had a Linux (native)
|
The CI for the Sys PR just hit a
|
After a long bisection, I found it present on all tried commits between trunk and β1 (included): https://github.com/shym/multicoretests/actions/runs/3517413388/jobs/5895155218#step:11:831 but I didn’t manage to get a seed that give reproducibility. |
Maybe another issue should be opened, but I indeed saw quite a few issues on native code:
|
Another
|
Also seen on Windows
|
Again observed on Linux
|
On Linux trunk bytecode, this weird result:
|
That's a strange error indeed! |
Not spotted since the release of |
From #88:
Ephemeron
test ontrunk
https://github.com/jmid/multicoretests/actions/runs/3444725852/jobs/5747632136#step:8:851Originally posted by @jmid in #88 (comment)
Ephemeron
GC-fix was cherry picked to5.0~trunk
21 days ago: Fix ephemeron assertion by allowing for data values that are in the minor heap ocaml/ocaml#11631I'm wondering whether it is a fresh issue - or caused by one of these that somehow haven't propagated through to install via
5.0.0~trunk
and setup-ocaml...The text was updated successfully, but these errors were encountered: