On Jun 26 11:19, [EMAIL PROTECTED] wrote: > We casually encountered some test cases failed randomly with > > “caught signal 15, not SIGSEGV”. > > We found that signal 15 came from PAN, but haven’t found the root cause. > Anyone here has similar problems? > > here are some of those cases for reference: > > capset02 > clone03 > clone06 > setrlimit01
Do you have the section of test log where this occurs. PAN has an all-stop flag (-A, IIRC) which will cause PAN to kill off running test cases if one fails. Are you running the tests in parallel (-x N, N > 1) with the all-stop flag? Nate ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
