Re: parallel test failures

2021-02-27 Thread David Bremner
Tomi Ollila writes: > So, AFAIU, you got 124 since timeout(1) exited with that status (and > killed all parallel(1) executions (after 2 minutes in that case?)... > ... and when you set NOTMUCH_TEST_TIMEOUT=0 then timeout(1) was not > executed and a test hung (probably T355-smime). That sounds

Re: parallel test failures

2021-02-27 Thread Tomi Ollila
On Fri, Feb 26 2021, David Bremner wrote: > David Bremner writes: > >> >> Thanks to both of you for your feedback / suggestions. I did read today >> that timeout exits with 124 when the time limit is reached. I haven't >> investigated further (nor do I know how the timelimit should be reached,

Re: parallel test failures

2021-02-26 Thread David Bremner
David Bremner writes: > Tomi Ollila writes: > >> >> Anyway, the log.gz did not show any tests failing but parallel exiting >> nonzero possibly for some other reason. Cannot say. Probably stracing (even >> with --seccomp-bpf) would make it happen even less likely :/ >> > > Thanks to both of you

Re: parallel test failures

2021-02-26 Thread David Bremner
Tomi Ollila writes: > > Anyway, the log.gz did not show any tests failing but parallel exiting > nonzero possibly for some other reason. Cannot say. Probably stracing (even > with --seccomp-bpf) would make it happen even less likely :/ > Thanks to both of you for your feedback / suggestions. I

Re: parallel test failures

2021-02-25 Thread Tomi Ollila
On Fri, Feb 19 2021, David Bremner wrote: > I have intermittent failures when running the test suite on sufficiently > parallel machines. I have attached a log of such a failing build, > although it does not seem especially illuminating. > > It takes anywhere from 5 to 300 runs to get a failure

Re: parallel test failures

2021-02-21 Thread Xu Wang
I did not look at logs, but I have had problem in other scenarios. The way I debugged was to use strace to get a list of all files the tests accessed. From that list I could recognize that some files that should have been in separate temp directories were not thread-specific and solution was to

parallel test failures

2021-02-19 Thread David Bremner
I have intermittent failures when running the test suite on sufficiently parallel machines. I have attached a log of such a failing build, although it does not seem especially illuminating. It takes anywhere from 5 to 300 runs to get a failure for me running on 60 hardware threads (30 cores).