If you look at [1], it seems that fedora-cloud-tests ran smoothly, all green steps. But looking closely at [2], you notice that there were crashes, VMs weren't even started. While I fixed the issue that caused VMs not to be started, the check shouldn't fail silently like this.
Please fix fedora-cloud-tests, and possibly atomic check too, in a way that if such error occurs, raise an exception so the check crashes and buildbot notices.
[1] http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/398103 [2] http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/398103/steps/runtask/logs/taskotron-stdio.log
This ticket had assigned some Differential requests: D1170
So it looks to me like it actually did what it's supposed to do: reported NEEDS_INSPECTION. It failed to grab the image because the value for the Cloud Base image was wrong, and ansible couldn't reach the VM. I'll fix it and submit a patch.
! In #928#13358, @roshi wrote: So it looks to me like it actually did what it's supposed to do: reported NEEDS_INSPECTION. It failed to grab the image because the value for the Cloud Base image was wrong, and ansible couldn't reach the VM. I'll fix it and submit a patch.
The thing is that it was a bug in our infrastructure (a bug in trigger), this shouldn't have been reported as NEEDS_INSPECTION, this should have crashed so we could have gotten an e-mail about it from buildbot so we could fix it.
NEEDS_INSPECTION is an outcome for package/compose maintainers saying that the check for the item (package/compose) has kind of passed (for the lack of better term) but there were some issues that should be looked at.
At least this is the current state we have now, this will need to change with dist-git tasks, and the new execdb with be part of that.
I'd put this response in the task that was being called - as I thought it fit what "NEEDS_INSPECTION" was supposed to be. I've updated the task to report "FAILED" in these instances, so we'll see a failure in this case. Closing this issue.
I don't think that's a FAILED, honestly. If the images don't work - that's an execution error, not a test failure
FAILED
! In #928#13385, @tflink wrote: I don't think that's a FAILED, honestly. If the images don't work - that's an execution error, not a test failure
Yes, as I stated in the description, task needs to raise an exception and crash so we get notified.
I'm updating the tasks to throw an exception if it can't get the image.
This has been resolved, closing.
Metadata Update from @kparal: - Issue close_status updated to: Fixed
Login to comment on this ticket.