Description of problem:
I have a job which should be finished, but web ui shows it is 50% in progress:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I have seen it before: this happens when there is no result in a task.
It is questionable whether this should be considered a bug in the task or in the scheduler - in any case it would need documenting.
The options are:
Unless the test returns a result it does not fail nor succeed. Fix the test.
Unless the test fails explicitly it should be considered Pass.
Each approach has its Pros and Cons...
There is reserving job which I returned the machines by 'return2beaker', but it shows 75% in running state, though all recipes are finished.
Han, I think what you see now is different issue and this time something is wrong indeed. I am cloning the bug.
Taking this: harness should handle it, when there is no result.
*** Bug 627870 has been marked as a duplicate of this bug. ***
Fix tested in a VM. Brewing RPMs to test on stage.