Hide Forgot
Description of problem: Some tasks are left in running state, and don't seem to make to it "Completed". So when recipe is "finished" I have: Task 1 - Completed Task 2 - Completed ... Task M - Running ... Task N - Completed/Waiting It appears that tests actually executed, and in "debug/.task_beah_raw" I see listed log files, so I'm assuming, that beah did try to upload these. Version-Release number of selected component (if applicable): How reproducible: sporadicly Steps to Reproduce: unknown, my guess would be to run job with many tasks Actual results: Some tasks are left in running state. Expected results: Task should eventually make it to "Completed". Additional info:
they won't run forever because the watchdog will eventually get them.
From this console log it looks like transient error between LC and Scheduler: http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2011/12/1737/173756/364205/console.log 'Fault: <Fault 1: "<class \'turbogears.identity.exceptions.IdentityFailure\'>: Please log in first"> Harness tries to repeat calls when there is network error, but it does not repeat all calls when there are errors reported by Scheduler. The problem is we do not want it to stuck on a single call. There is a Bug 636093 to improve this.
Bulk reassignment of issues as Bill has moved to another team.
This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration. Please feel free to reopen the bug with additional information and/or business cases behind it.