public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cseo at linux dot vnet dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5542] New: TestRunner hangs on 'testStoppedAckDaemon(frysk.proc.TestProcStopped)'
Date: Fri, 04 Jan 2008 17:58:00 -0000	[thread overview]
Message-ID: <20080104175747.5542.cseo@linux.vnet.ibm.com> (raw)

1. Overview

TestRunner is hanging at 100% CPU on this test, when running the labrat script
on ppc64. Test log shows:

---
(lots of tests before...)
Running testGetExe(frysk.proc.TestProcGet) ...PASS
Running testStoppedAckDaemon(frysk.proc.TestProcStopped) ...
---


2. Steps to reproduce

- Download the labrat script (build_farm.sh).
- Run the script.

3. Results

After some minutes running, you'll notice that TestRunner is at 100% CPU and the
test doesn't proceed. If you take a look at the logs, you'll find the same lines
as shown above.

The expected result would be the completion of this testsuite run.

Found on frysk-git, 2007-12-20, on RHEL5 running the Fedora 8 kernel. 'uname -a'
output:

Linux bart.ltc.br.ibm.com 2.6.23.1-42kdump #2 SMP Thu Dec 20 12:00:42 BRST 2007
ppc64 ppc64 ppc64 GNU/Linux

Hardware: 4-way POWER5+

-- 
           Summary: TestRunner hangs on
                    'testStoppedAckDaemon(frysk.proc.TestProcStopped)'
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cseo at linux dot vnet dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5542

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


                 reply	other threads:[~2008-01-04 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080104175747.5542.cseo@linux.vnet.ibm.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: link
Be 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).