On Thu, Nov 12, 2020 at 5:46 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
On Thu, Nov 12, 2020 at 4:01 PM Nir Soffer <nsoffer(a)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_s...
>
> Can someone look at the network suite failures?
>
Network suite has indeed been failing randomly recently. More often than
not it was due to timeouts while waiting for connections to the hosts,
timeouts while waiting for hosts to reach deserted statuses, and in the
above I also see what looks like a sock error on port 22. Not only are the
failing tests random but also usually the next nightly passes. This leads
me to believe that the cause of the failures is outside the scope of the
tests code.
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_s...
- 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.
+1
_______________________________________________