From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20628 invoked by alias); 12 Jan 2007 09:12:57 -0000 Received: (qmail 20551 invoked by uid 48); 12 Jan 2007 09:12:40 -0000 Date: Fri, 12 Jan 2007 09:12:00 -0000 From: "jan dot kratochvil at redhat dot com" To: frysk-bugzilla@sourceware.org Message-ID: <20070112091240.3864.jan.kratochvil@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/3864] New: Tests timeout is too short X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00079.txt.bz2 List-Id: 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.