Opened 12 years ago
Last modified 10 years ago
#1238 new defect
IZ297: throughput test waits infinetely
Reported by: | pollinger | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | testsuite | Version: | current |
Severity: | minor | Keywords: | tests |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=297]
Issue #: 297 Platform: All Reporter: pollinger (pollinger) Component: testsuite OS: All Subcomponent: tests Version: current CC: None defined Status: NEW Priority: P1 Resolution: Issue type: DEFECT Target milestone: milestone 1 Assigned to: issues@testsuite QA Contact: joga URL: * Summary: throughput test waits infinetely Status whiteboard: Attachments: Issue 297 blocks: Votes for issue 297: Vote for this issue Opened: Tue May 5 02:00:00 -0700 2009 ------------------------ When there is an error during the throughput test, the throughput test never ends. In my case, the throughput test is in scenario 0 and all tp*@* queue instances are in Error state. There are about 300 jobs waiting to be scheduled, and the throughput test waits infinitely - assumedly for the jobs to be scheduled. It should exit with an severe error, instead. Btw.: The throughput test should print that it is the throughput test - it deletes the screen, so there is no way to see what test it currently is. ------- Additional comments from pollinger Fri Dec 4 02:54:49 -0700 2009 ------- In the 6.2u5 QA we saw two cases where the throughput test got into this endless loop. One time the qevent client was built with the wrong compiler and crashed, one time the qevent client had the wrong GDI version. The testsuite could easily capture these error reasons that are always very likely.
Change History (1)
comment:1 Changed 10 years ago by dlove
- Priority changed from highest to normal
- Severity set to minor
Note: See
TracTickets for help on using
tickets.