Open zoffixznet opened 7 years ago
@zoffixznet does this still flop after PR #11 ?
@zoffixznet 🙋
@zoffixznet does this still flop after PR #11 ?
Yes, tho now it's due to Test.pm not being thread-safe. I think with the new atomic ops we can make it fix that (at least the part that make the tests flop).
Gonna do it after sleep.
On closer inspection, making Test.pm thread-safer isn't just editing a couple of lines. Even if the variables are handled safely, the printing of output itself can come out of order, so I'd say Test.pm6 will be thread-unsafe for quite some time.
(in my homegrown Testo
module, I'll look into addressing this issue, once I find some time to work on that module)
This has to be reopened then.
FWIW, an easy way to fix it in this module is to just setup a Channel that receives closures and runs them and feed it with tests to run; then output will always be in order. Untested, but it works in my head :)
If you repeatedly run the test suite, once in a while a test dies with send-on-closed channel error: