On Thu, Nov 12, 2020 at 4:01 PM Nir Soffer <nsoffer@redhat.com> wrote:
I had many failures in recent OST patches, so I posted this change: https://gerrit.ovirt.org/c/112174/
This patch does not change anything, but it modifies the lago vm configuration so it triggers 8 jobs. 2 network test suites failed: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_stan...
Can someone look at the network suite failures?
If these suites are not stable, we should not included them in the CI for OST patches, or mark them as expected failures so they do not fail the build.
I triggered another build since I see lot of random failures in other suites.
On the next build - different errors: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_stan... - basic_suite_4.3.el7.x86_64 - failed - basic_suite_master.el7.x86_64 - failed - network_suite_4.3.el7.x86_64 - failed - network_suite_master.el7.x86_64 - failed With the current state OST CI is not useful to anyone. Builds take hours and fail randomly. This wastes our limited resources for other projects and makes contribution to this project very hard.