-
Notifications
You must be signed in to change notification settings - Fork 16
Labels
test suite reliabilityIssue concerns tests that should behave more predictablyIssue concerns tests that should behave more predictably
Description
Since adding agree_prop_par_asym to STM_domain in #315 we have seen occasional cases of the _ ref test parallel asymmetric failing to trigger.
Here's a fresh case from yesterday, on Cygwin part2 running trunk (5.2.0):
https://github.com/ocaml-multicore/multicoretests/actions/runs/5201990235/jobs/9388312861
random seed: 513749813
generated error fail pass / total time test name
[...]
[ ] 0 0 0 0 / 2000 0.0s STM int ref test parallel asymmetric
[ ] 1501 0 0 1501 / 2000 395.8s STM int ref test parallel asymmetric
[✗] 2000 0 0 2000 / 2000 410.2s STM int ref test parallel asymmetric
[...]
Previously this was observed
- in Opam installation updates #346 on macOS 5.1 with
int64 ref test parallel asymmetric - in A few 4.14 updates #339 on Windows trunk
int ref test parallel asymmetric - in Chore: src/neg_tests cleanups #330 on Cygwin trunk and 5.1 with
int ref test parallel asymmetricandint64 ref test parallel asymmetric
It would be nice to use statistics as outlined in #362 to improve the functionality to be more stable.
A fix may involve switching away from a Semaphore.Binary as @shym was originally asking about
#315 (comment)
Metadata
Metadata
Assignees
Labels
test suite reliabilityIssue concerns tests that should behave more predictablyIssue concerns tests that should behave more predictably