Open olexandr-konovalov opened 5 years ago
Same can be observed on Travis: https://travis-ci.org/gap-packages/JupyterKernel/jobs/479808058 (it does not fail the test and remain unnoticed?). My guess is that because of calling IO_fork()
, at some point we have two processes running the same test.
See also #98 for the fix of the issue with test failure detection on Jenkins.
What happens here in version 1.1?
#I No errors detected while testing
appears twice and breaks testing scripts, and 2nd time the timing is negative: