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] Segfault in STM Domain.DLS test sequential
on 32-bit trunk
#446
Comments
I wonder if it is related to #12889, the only recent change to Domain.DLS that I can think of. (I hope not!) |
This just triggered again on 32-bit
|
Is there more information that we can use to try to investigate this? "There is a segfault somewhere in Domain.DLS on 32bit" is not that much. |
First off, this is a collection of failures we observe.
Come on, there are QCheck seeds that caused the failures, GA workflows listing the steps taken, and links to 2 CI run logs, with full information about versions.
|
No snark intended, I genuinely wonder how you work with these failures. For example I'm not sure if it is reasonably easy to extract a backtrace, and/or to observe the same failure within the debug runtime. (Is this segfault due to a memory corruption, or an assert failure?) If you prefer to work on this without upstream looking over your shoulder for now, I am happy to let you work your magic and wait for easier reproduction instructions. |
OK, fair enough. I've been trying today for this one: https://github.com/ocaml-multicore/multicoretests/actions?query=branch%3Adomain-dls-32-bit-focus
|
I finally managed to reproduce this one - on 5.2.0 - and only once for now. It is indeed a sequential fault! 😮
|
Switching hard-coded seed to 107236932 (the first one) works much better! |
In the CI-run for #445 on 32-bit trunk the
STM Domain.DLS test sequential
triggered a segfaulthttps://github.com/ocaml-multicore/multicoretests/actions/runs/8436771284/job/23104952265?pr=445
This may be another case of a 32-bit/bytecode issue showing up in a couple of different tests:
Surprisingly this case however triggered in a sequential (single-domain) test! 😮
The text was updated successfully, but these errors were encountered: