Bug 681005 - [Beaker][Harness] Recipes not completing as expected.
Summary: [Beaker][Harness] Recipes not completing as expected.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.6
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: ---
Assignee: Marian Csontos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-28 18:40 UTC by Jeff Burke
Modified: 2019-05-22 13:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-03 20:32:56 UTC


Attachments (Terms of Use)

Description Jeff Burke 2011-02-28 18:40:09 UTC
Description of problem:
 When running kernel testing I have noticed recipes not completing properly.

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

How reproducible:
 Intermittent 

Actual results:
 If you look at the console log: 
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/02/568/56861/116039/console.log

Everything looks like it is fine. It looks like it reported the last test as finished and it should start running the next test. But it never does.

Job, https://beaker.engineering.redhat.com/jobs/56861 Recipe, 116039

Expected results:
 Testing should continue as expected.

Additional info:

Comment 1 Jeff Burke 2011-02-28 21:07:26 UTC
Here is another instance of the same thing on a different job.
Job, https://beaker.engineering.redhat.com/jobs/57370 Recipe, 117119

Everything looks like it is fine. It looks like it reported the last test as
finished and it should start running the next test. But it never does.

Comment 2 Marian Csontos 2011-02-28 22:20:38 UTC
I have found and fixed a race condition. Will write and run a test to check it works as expected.

Comment 3 Marian Csontos 2011-03-01 13:28:09 UTC
Job with the fix: https://beaker.engineering.redhat.com/jobs/57690

Job w/o the fix: https://beaker.engineering.redhat.com/jobs/57689 - the job does not EWD thanks to my intervention to get more significant statistical data.

So far the failure ratio is 5/28 to 0/35 and counting.


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