On Fri, Apr 27, 2018 at 5:57 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
On Fri, Apr 27, 2018 at 7:34 PM, Dafna Ron <dron@redhat.com> wrote:You can read more about the issue and how it was resolved here:I am glad to report that the issue with CQ alerts was resolved thanks to Barak and Evgheni.Hi,I wanted to give a short status on this week's failures and OST current status.
https://ovirt-jira.atlassian.net/browse/OVIRT-1974 How was the VM2 high-performance with vNUMA and pinned to more than one host (a race) was solved?
I was not seeing it all week, however, we had just had a failure for that today: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7169/
the change reported: https://gerrit.ovirt.org/#/c/8Currently we have one on-going possible regression which was reported to the list and to Arik.9852/ - examples: upload ova as a virtual machine template.you can view the details in this Jira: https://ovirt-jira.atlassian.net/browse/OFT-648 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).Y.
I noticed the "example" but since it was reported as a failure I wanted to make sure nothing in the "example" caused the failure which is why I sent to the list and asked Arik to have a look.
There was an infra issue with Mirrors not being available for a few minutes. the issue was momentarily and was resolved on its own.You can see the Jira to these two issues here: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.
https://ovirt-jira.atlassian.net/browse/OFT-605
https://ovirt-jira.atlassian.net/browse/OFT-612
https://ovirt-jira.atlassian.net/browse/OFT-606 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 outages
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:Thanks,Dafna
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel