multicoretests
multicoretests copied to clipboard
PBT testsuite and libraries for testing multicore OCaml
Most of the non-STM/Lin tests were written before repeat and retry found their current forms. These tests could benefit from being updated to use them (to increase reproducability): - ./src/domain_spawntree.ml...
We should consider updating the vertical printer to use `Format` (as function values are printed terribly)
4 weeks back the scheduled `trunk` tests failed to find a Bigarray STM test counterexample on MSVC bytecode: https://github.com/ocaml-multicore/multicoretests/actions/runs/9932690046/job/27434370275 ``` random seed: 171860057 generated error fail pass / total time...
(This PR is based on top of #462, which it depends on.) The new module `Dynarray` has a rather tricky implementation as it is not designed for parallel use, but...
The `STM Sys test parallel test` on s390x with OCaml 5.1.0 found an unexpected counterexample: https://ocaml-multicoretests.ci.dev:8100/job/2024-07-05/135811-ci-ocluster-build-a950ab ``` random seed: 462089430 generated error fail pass / total time test name [...
Add gc tests
This PR adds initial tests of the `Gc` module - and in particular testing of `Gc.compact`. Exercising `Gc.counters` already triggered a known issue locally, which has recently been fixed on...
The upcoming `Gc` test in #469 has surfaced a macOS segfault while running `STM Gc stress test parallel`. This first happened on 5.3.0+trunk: https://github.com/ocaml-multicore/multicoretests/actions/runs/11010731348/job/30573309071 ``` random seed: 464277843 generated error...
Motivated by bugs rarely occurring with glibc
MSVC 32bit workflows came up in #473 and may help catch 64bit-isms early.
The new Gc test in #469 triggered an assertion failure in Linux debug 5.3.0+trunk: https://github.com/ocaml-multicore/multicoretests/actions/runs/10581716289/job/29319700079?pr=469 ``` random seed: 369983017 generated error fail pass / total time test name [ ]...