[ovirt-devel] Re: RFC: Not Failing OST on Missing Artifact During Collection
On Wednesday, January 29, 2020, Anton Marchukov <amarchuk(a)redhat.com> wrote:
Hello All.
I faced it multiple times during local runs, e.g. first it was missing
/tmp/otopi*. Now it fails for me on missing
/var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log
and /etc/dnf on centos7 engine. It seems like any missing artifact during
collection step will fail the test.
I understand some potential benefit of it, but I suggest we do not fail it
if we are unable to find any of the artifacts during collection step.
Better just to issue a warning in the logs and go on. If somebody needs to
test for particular log presence, I suggest it should be included as a test
step instead.
Wdyt?
+1
A step further,
Could be very helpful if we could select the suites for OST during its
launch since many times we are only interested in a specific component.
For example: only run storage suite and don't care for ui browser suite
when checking a storage change. This way we can avoid OST being shut
completely when only one suite is broken which is not relevant to the
change being verified.
--
Anton Marchukov
Associate Manager - RHV DevOps - Red Hat
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-
guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/
message/J3JZ337UJMBRBGUBPUIRA2T5NMNNPGE6/
Attachments:
- attachment.html (text/html — 2.3 KB)