Jan Midtgaard
Jan Midtgaard
After a good round of testing this afternoon I can confirm that this fixes both #13512 and #13402. Thank you both!
This one is easily reproducible. I've commented out the sequential test and can trigger the assertion failure on every run, regardless of the seed: ``` $ OCAMLRUNPARAM="s=4096,v=0,V=1" dune exec src/gc/stm_tests.exe...
This is known upstream as a sporadic failure ocaml/ocaml#13090. I've shared a standalone reproducer on that issue.
I've arrived at a simpler reproducer and shared details here on the upstream issue: https://github.com/ocaml/ocaml/issues/13090#issuecomment-2596016823
This has now been fixed upstream on `trunk` in ocaml/ocaml#13774 but may continue to trigger on 5.3.
Fair enough. However I don't get why PRs that have been opened since, e.g. in the past couple of days, have been allocated CI resources and apparently completed their jobs:...
This times out on MSVC bytecode and MinGW bytecode trunk, where I suspect the underlying buffer size to differ.
LGTM, great to have a growing list of example findings! :tada: Two observations: - This is meant to document to new-comers that the tool is useful in practice. As such,...
I can still trigger the ~~bug~~ assertion failure with the above patch :grimacing: I've also built a compiler switch with TSan enabled (`CFLAGS=-DTSAN_INSTRUMENT_ALL`) to see if that would trigger a...
Here's an update: - I've been able to trigger the assertion failure under macOS (after 7h!) and under an Alpine Docker image, which should help clear glibc from blame -...