public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3864] New: Tests timeout is too short Date: Fri, 12 Jan 2007 09:12:00 -0000 [thread overview] Message-ID: <20070112091240.3864.jan.kratochvil@redhat.com> (raw) Debugging frysk under gdb adds too much overhead and with the all-time-swapping frysk it will fail on: (gdb) r Starting program: /home/jkratoch/redhat/frysk-build/frysk-core/TestRunner -r 1000 testStressMultiThreadedDetach\(frysk.util.StressTestFStack\) [Thread debugging using libthread_db enabled] [New Thread -1208522512 (LWP 15307)] [New Thread -1210623088 (LWP 15702)] Running testStressMultiThreadedDetach(frysk.util.StressTestFStack) ...[New Thread -1221112944 (LWP 15770)] PASS Time: 36.884 OK (1 test) ... Running testStressMultiThreadedDetach(frysk.util.StressTestFStack) ...FAIL junit.framework.AssertionFailedError: event loop run explictly stopped (perform backtrace) Time: 9.603 There was 1 failure: 1) testStressMultiThreadedDetach(frysk.util.StressTestFStack)junit.framework.AssertionFailedError: event loop run explictly stopped (perform backtrace) at frysk.proc.TestLib.assertRunUntilStop(TestRunner) at frysk.proc.TestLib.assertRunUntilStop(TestRunner) at frysk.util.TestFStack.multiThreaded(TestRunner) at frysk.util.StressTestFStack.testStressMultiThreadedDetach(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner) FAILURES!!! Tests run: 1, Failures: 1, Errors: 0 It looks as frysk testsuite goes the same way as gdb testsuite where many testcases have instable results depending on various races. Any timeout should be >=300 seconds and it should be exhausted only in the FAIL case. -- Summary: Tests timeout is too short Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: jan dot kratochvil at redhat dot com GCC host triplet: i686-pc-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=3864 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-01-12 9:12 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-12 9:12 jan dot kratochvil at redhat dot com [this message] 2007-01-12 9:14 ` [Bug general/3864] " jan dot kratochvil at redhat dot com 2007-01-19 22:40 ` cagney at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070112091240.3864.jan.kratochvil@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).