Bug #9339
closedIncorrect progress report
0%
Description
When I have, say, 2 validation sub-jobs when the first one is solved successfully while the second one fails in VOG and no task is generated, I get the following reason of a corrupted decision from Bridge: "The job didn't got full tasks progress data".
Updated by Ilja Zakharov almost 5 years ago
- Status changed from New to Feedback
This is very bad example. VTG should not fail ever, if it fails then all results might be completely spoiled. Currently I do not know any feasible example when VTG failing is expected. So your example is artificial and seems that you got it during development process.
P.S. I tried to reproduce your example by providing wrong configuration options but VTG still does not fail in such cases.
Updated by Evgeny Novikov almost 5 years ago
- Status changed from Feedback to New
Ilja Zakharov wrote:
This is very bad example. VTG should not fail ever, if it fails then all results might be completely spoiled. Currently I do not know any feasible example when VTG failing is expected. So your example is artificial and seems that you got it during development process.
P.S. I tried to reproduce your example by providing wrong configuration options but VTG still does not fail in such cases.
Please, see the issue description more accurately. I said about VOG (now it is PFG). Second, of course sub-jobs are for development purposes primarily, but nothing should fail in so bad way. I am not sure that one year issue still exists, but you can try to create a job with two sub-jobs and different build bases. For the second sub-job you can try to verify those modules that are not in a build base.
Updated by Evgeny Novikov almost 5 years ago
At last, any program can unexpectedly fail. Even if this is impossible right now and you have proved that mathematically, you can't ensure that a student will not add something that will cause some tricky failures.
Updated by Evgeny Novikov almost 5 years ago
- Status changed from New to Resolved
Ilja has fixed this issue one day in the past. The fix is in master already.
Updated by Evgeny Novikov almost 5 years ago
- Status changed from Resolved to Closed