|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
Test cases randomly failed with "caught signal 15, not SIGSEGV"Hi, 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 Roy ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ltp-list mailing list Ltp-list@... https://lists.sourceforge.net/lists/listinfo/ltp-list |
|
|
Re: Test cases randomly failed with "caught signal 15, not SIGSEGV"On Thu, 2008-06-26 at 11:19 +0800, roylee@... wrote:
> Hi, > > > > 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? No Roy. I have not encountered any such problem till now. Please check out the May 2008 LTP release run on i386, x86_64, ia64, ppc64 and s390x. They all have passed properly on those architectures: http://nchc.dl.sourceforge.net/sourceforge/ltp/ltp-full-20080531_results_kernel-2.6.18-8.el5_architecture-x86_64.html http://nchc.dl.sourceforge.net/sourceforge/ltp/ltp-full-20080531_results_kernel-2.6.18-53.1.13.el5_architecture-i386.html http://nchc.dl.sourceforge.net/sourceforge/ltp/ltp-full-20080531_results_kernel-2.6.16.21-0.8-ppc64_architecture-ppc64.html http://nchc.dl.sourceforge.net/sourceforge/ltp/ltp-full-20080531_results_kernel-2.6.16.21-0.8-default_architecture-s390x.html http://nchc.dl.sourceforge.net/sourceforge/ltp/ltp-full-20080531_results_kernel-2.6.16.21-0.8-default_architecture-ia64.html Regards-- Subrata > > > > here are some of those cases for reference: > > > > capset02 > > clone03 > > clone06 > > setrlimit01 > > > > > > Roy > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ Ltp-list mailing list Ltp-list@... https://lists.sourceforge.net/lists/listinfo/ltp-list ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ltp-list mailing list Ltp-list@... https://lists.sourceforge.net/lists/listinfo/ltp-list |
|
|
Re: Test cases randomly failed with "caught signal 15, not SIGSEGV"On Jun 26 11:19, roylee@... 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 Ltp-list@... https://lists.sourceforge.net/lists/listinfo/ltp-list |
| Free Forum Powered by Nabble | Forum Help |