The build-artifacts are the developer's responsibility and is not related
to CQ.
it does not actually matter though why the build-artifacts failed as there
are passing builds after this failure which means the project would have a
passing package to be tested by CQ which include the changes that
On Wed, Jun 19, 2019 at 7:03 PM Dafna Ron wrote:
> this was a failed build-artifacts.
> its now fixed as there are several passing builds after this one
>
Why build-artifacts failed?
Do we have a retry on failures?
> On Wed, Jun 19, 2019 at 3:16 AM oVirt Jenkins wrote:
>
>> A system test
this was a failed build-artifacts.
its now fixed as there are several passing builds after this one
On Wed, Jun 19, 2019 at 3:16 AM oVirt Jenkins wrote:
> A system test invoked by the "ovirt-master" change queue including change
> 100778,6 (vdsm) failed. However, this change seems not to be the
A system test invoked by the "ovirt-master" change queue including change
100778,6 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 100783,7 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.
This change
