Bug 435718 - HTS should run suspend to run first
Summary: HTS should run suspend to run first
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 5
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-03 15:04 UTC by Greg Nichols
Modified: 2008-09-12 16:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-12 16:54:20 UTC
Embargoed:


Attachments (Terms of Use)
hts test plan (1.80 KB, text/xml)
2008-06-20 07:16 UTC, Hao Liu
no flags Details

Description Greg Nichols 2008-03-03 15:04:12 UTC
HTS should schedule the suspend test to run before all other tests on systems
where it is required.    Currently, suspend is scheduled as the last interactive
test.

Version:

HTS 5.1 R4

Comment 1 Greg Nichols 2008-03-06 15:53:45 UTC
Fixed in R5

Comment 4 Greg Nichols 2008-06-19 18:10:32 UTC
Please provide information about the system configuration, as well as
/var/hts/plan.xml for the error causing this bug to be re-opened.

Comment 5 Hao Liu 2008-06-20 07:16:58 UTC
Created attachment 309909 [details]
hts test plan

Comment 6 Hao Liu 2008-06-20 07:17:30 UTC
The bug is not fixed in hts5.2-17:
I ran "#hts certify --test info" on my test machine. suspend test was not
scheduled as the first one to run, the first one is still the info test.

Below is the system configuration of my test machine:

---package info---
#rpm -q hts dt stress lmbench
hts-5.2-17.el5
dt-15.14-2.EL5
stress-0.18.8-1.3.EL5
lmbench-3.0a7-6.EL5

---system info---
#cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.2 (Tikanga)

#uname -a
Linux dhcp-65-86.nay.redhat.com 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT
2008 i686 athlon i386 GNU/Linux



Comment 7 Greg Nichols 2008-06-25 18:25:35 UTC
Please attach /var/hts/plan.xml


Note You need to log in before you can comment on or make changes to this bug.