WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 132] New: LTP alarm04 test fails in current unstable

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 132] New: LTP alarm04 test fails in current unstable
From: pl@xxxxxxxxxx
Date: Tue, 02 Aug 2005 16:38:25 +0000
Delivery-date: Tue, 02 Aug 2005 16:38:29 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=132

           Summary: LTP alarm04 test  fails in current unstable
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: pl@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx


Looks like the LTP alarm04 test started failing sometime between the July 12 and
July 13 daily build.

bl3-3-20050712-03:00/domains/bl3-3/results/LTP/runltp.output:sig_rev     1  PASS
 :  Functionality of alarm(3) successful
bl3-3-20050713-17:02/domains/bl3-3/results/LTP/runltp.output:sig_rev     1  FAIL
 :  alarm() fails to send SIGALRM to execede process

/*
 * Test Name: alarm04
 *
 * Test Description:
 *  Check that when an alarm request is made, the signal SIGALRM is received
 *  even after the process has done an exec().
 *
 * Expected Result:
 *  The signal SIGALRM should be received in the execed process.
 *  Since, this process execs another process, hence never returns unless
 *  exec fails.

Looking through changesets to try to narrow this down a bit.



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

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 132] New: LTP alarm04 test fails in current unstable, pl <=