This adds a longer explanation when some check is aborted because of a
missing build in an update (which means that the update got edited
during the check execution). A list of such missed builds is printed
out. This should make it easier for readers to understand what's going on.
A safety check for build2update() correctness was removed, it's better
to put these safety checks directly into build2update() method.
The explanation now looks like:
not ok - depcheck for Bodhi update NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22 # FAIL
---
arch: i386
details:
output: |-
Update was incomplete - not all builds from this update have been tested. This can happen when the update is edited in Bodhi during the check execution.
Builds which haven't been tested:
NetworkManager-openconnect-1.0.2-1.fc22
item: NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22
outcome: ABORTED
summary: NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22
into F22 testing
type: bodhi_update
...The safety check (everything connected to untested_builds variable) was instead put directly into build2update(), it will be a separate diff against libtaskotron.