Bug 677289 - run time is restricted to 2.5 hours while the TestTime is set to 48 hours in the Makefile
Summary: run time is restricted to 2.5 hours while the TestTime is set to 48 hours in ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
Assignee: Marian Csontos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-14 09:24 UTC by Han Pingtian
Modified: 2012-06-15 08:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-15 06:31:00 UTC


Attachments (Terms of Use)

Description Han Pingtian 2011-02-14 09:24:04 UTC
Description of problem:
I have a job which now always timeouted since it is restricted to run only 2.5 hours but I have set the 'TestTime' to '48h' in the Makefile.

The job is:
https://beaker.engineering.redhat.com/jobs/52701

The testcase is /kernel/Fujitsu/rhts_autokdump.

The job can run about 11 hours previously:

https://beaker.engineering.redhat.com/jobs/38346

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Marian Csontos 2011-02-14 10:03:18 UTC
On the task's page [1] the expected time is 2h. And the task was modified between those two runs [2].

  [1] https://beaker.engineering.redhat.com/tasks/4930
  [2] Updated Date: 	2011-01-26 03:40:36

May be the task was not tagged when updated.
Try adding it to beaker again and make sure it's tagged properly.
If it still does not work, assign to Scheduler component as it's the Scheduler setting the duration.

Comment 2 Han Pingtian 2011-02-15 06:06:58 UTC
After make tag and make bkradd, the task's page shows the expected time is 2days. I have launched a new job:

https://beaker.engineering.redhat.com/jobs/53058

Comment 3 Marian Csontos 2011-02-15 06:31:00 UTC
Unfortunately there is no history of uploaded tasks but the most probable cause is the task was not updated correctly.


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