This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Re: Automated build-and-test result for 2007/03/19
- From: Mark Wielaard <mark at klomp dot org>
- To: Kris Van Hees <kris dot van dot hees at oracle dot com>
- Cc: frysk at sourceware dot org
- Date: Mon, 19 Mar 2007 16:32:58 +0100
- Subject: Re: Automated build-and-test result for 2007/03/19
- References: <20070319113353.GE18035@ca-server1.us.oracle.com>
Hi Kris,
On Mon, 2007-03-19 at 04:33 -0700, Kris Van Hees wrote:
> Results for last night's build-and-test runs on x86_64 (it hung the x86
> box so no results from that box right now).
Nice overview. Thanks.
> FAILED TESTS:
> frysk-core - testStoppedAckDaemon(frysk.proc.TestProcStopped)
> frysk-core - testStoppedDetached(frysk.proc.TestProcStopped)
> frysk-core - testRefreshZombie(frysk.proc.TestRefresh)
> frysk-core - testLineStepFunctionCall(frysk.rt.TestStepping)
> frysk-core - testLineStepIfStatementPass(frysk.rt.TestStepping)
> frysk-core - testLineStepIfStatementFail(frysk.rt.TestStepping)
> frysk-core - TestRunner
What is this test?
> frysk-gtk - code has Copyright notice
> frysk-gui - code has Copyright notice
> frysk-imports - frysk3228/LoggerParent
This is an XPASS right?
> frysk-imports - frysk3491/x-state
> frysk-imports - frysk3997/ptrace_step_sig
Fixed (or rather, worked around for now).
> BROKEN TESTS:
> frysk-core - testParser(frysk.dom.TestParser)
> frysk-core - testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)
> frysk-core - testSteppingtestInsertRemove(frysk.proc.TestBreakpoints)
> frysk-core - testSteppingAddLots(frysk.proc.TestBreakpoints)
These last 3 should now PASS.
> frysk-core - testMemoryReadWrite(frysk.proc.TestMemory)
> frysk-core - testMultiThreadedStoppedAckDaemon(frysk.proc.TestProcStopped)
> frysk-core - testMultiThreadedStoppedDetached(frysk.proc.TestProcStopped)
> frysk-core - testCloneThenKillAttached(frysk.proc.TestProcTasksObserver)
> frysk-core - testDeleteAttached(frysk.proc.TestProcTasksObserver)
> frysk-core - testSyscallRunning(frysk.proc.TestSyscallRunning)
> frysk-core - testDetachExitingMainTask(frysk.proc.TestTaskObserver)
> frysk-core - testDetachExitingOtherTask(frysk.proc.TestTaskObserver)
> frysk-core - testBlockingFibonacciFork(frysk.proc.TestTaskObserverBlocked)
> frysk-core - testExecSyscall(frysk.proc.TestTaskSyscallObserver)
> frysk-core - testCreateAttachedAddSyscallObserver(frysk.proc.TestTaskSyscallObserver)
> frysk-core - testTerminateExit47(frysk.proc.TestTaskTerminateObserver)
> frysk-core - testTerminateKillKILL(frysk.proc.TestTaskTerminateObserver)
> frysk-core - testTerminatingExit47(frysk.proc.TestTaskTerminateObserver)
> frysk-core - testTerminatingKillKILL(frysk.proc.TestTaskTerminateObserver)
> frysk-core - testTerminatedExit47(frysk.proc.TestTaskTerminateObserver)
> frysk-core - testTerminatedKillKILL(frysk.proc.TestTaskTerminateObserver)
> frysk-core - testStepOver(frysk.rt.TestRunState)
> frysk-core - testInstructionNext(frysk.rt.TestRunState)
> frysk-core - testStepOut(frysk.rt.TestRunState)
> frysk-core - testBacktrace(frysk.rt.TestStackBacktrace)
> frysk-core - testThreadedBacktrace(frysk.rt.TestStackBacktrace)
> frysk-core - testFramePushing(frysk.rt.TestStackBacktrace)
> frysk-core - testFramePopping(frysk.rt.TestStackBacktrace)
> frysk-core - testCoreFileCreated(frysk.util.TestFCore)
> frysk-core - testElfCoreHeader(frysk.util.TestFCore)
> frysk-core - testProgramSegmentHeader(frysk.util.TestFCore)
Wow, that is a lot of broken tests. Are the broken in general, or just
for newer/utrace-based kernels?
> ==============================================================================
> Package "frysk_incr" (2007/03/19 01:43:37 - 2007/03/19 01:56:13)
>
> Desc: Incremental update of the Frysk source code tree
> ==============================================================================
A quick scan doesn't show any differences between these runs. Do you
expect there ever to be one?
Cheers,
Mark