You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
~211s and 102 samples to find a counterexample
But then takes
~3600s (3811-211) to shrink it successfully one step,
~5357a (9167-3810) to shrink it successfully a second step
~346s (9513-9167) to shrink it successfully a third step
...
Note that 10000s corresponds to ~170m, or 2h50m.
The Weak module is challenged by its state being fragile to GC invocations, making reproducability challenging - also during shrinking. We should avoid spending time on needless reruns to reduce simple integer arguments under these circumstances:
On the merge to
main
of #463 we are seeing a timeout of the 5.3 bytecode workflow caused by excessive shrinking duringSTM Weak test parallel
:https://github.com/ocaml-multicore/multicoretests/actions/runs/12426416197/job/34694657567
It is taking
But then takes
Note that 10000s corresponds to ~170m, or 2h50m.
The
Weak
module is challenged by its state being fragile to GC invocations, making reproducability challenging - also during shrinking. We should avoid spending time on needless reruns to reduce simple integer arguments under these circumstances:multicoretests/src/weak/stm_tests.ml
Lines 33 to 42 in 2ef4b84
and also consider running each
Weak
test in a separate test executable, like #469 now does, rather than the current hoop jumping:multicoretests/src/weak/stm_tests.ml
Lines 117 to 120 in 2ef4b84
The text was updated successfully, but these errors were encountered: