On Fri, Apr 27, 2018 at 7:34 PM, Dafna Ron <dron(a)redhat.com> wrote:
I wanted to give a short status on this week's failures and OST current
I am glad to report that the issue with CQ alerts was resolved thanks to
Barak and Evgheni.
You can read more about the issue and how it was resolved here:
How was the VM2 high-performance with vNUMA and pinned to more than one
host (a race) was solved?
Currently we have one on-going possible regression which was reported to
the list and to Arik.
the change reported: https://gerrit.ovirt.org/#/c/89852/
upload ova as a virtual machine template.
you can view the details in this Jira: https://ovirt-jira.atlassian
I don't understand how that *example* script could have caused this
regression - in a complete different scenario (virt-sparsify fails because
of libguestfs issue).
The majority of issues we had this week were failed-build artifacts for
fc27. There were two different cases, one was reported to Francesco who was
already working on a fix to the issue and the second started and resolved
during the evening/night of Apr 26-27.
You can see the Jira to these two issues here:
There was an infra issue with Mirrors not being available for a few
minutes. the issue was momentarily and was resolved on its own.
*Below you can see the chart for this week's resolved issues but cause of
failure:**Code* = regression of working components/functionalities
*Infra* = infrastructure/OST Infrastructure/Lago related issues/Power
*OST Tests* = package related issues, failed build artifacts
*Below is a chart showing failures by suite type: *
*Below is a chart showing failures by version type: *
*Below you can see the number of reported failures by resolution status:*
Devel mailing list