2014-11-06 14:12 GMT+01:00 Thomas D. <[email protected]>: > Hi, > > On 2014-11-05 22:20, David Lang wrote: > >> The test suite should have aborted/failed with that error... if I > >> wouldn't have stopped the test suite, it would be still running... > > > > actually, would it run forever or was it just running other tests? > (since it > > takes about 90 min to run the full set of tests) > > > > If it is hitting a fatal error that stops all future tests without > exiting, that > > is a problem, but it's not clear that it is stuck. > > Well, all the tests before were finished within ~2 minutes (=every 2 > minutes I got a new output). Also I was able to follow the test in ps/htop. > > So from my view, no other tests were running. The failing test was > idling, only new "mssleep 100" processes were spawned... > > By the way, the failing test was caused by a contribution to the testbench I merged yesterday and todays testbench runs captured that problem.
Nevertheless, I have set aside the rest of the week to try to iron out at least most of these types of issues. It's also not nice for me having test that potentially hang. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
