Commit Graph

2 Commits

Author SHA1 Message Date
Ed Santiago
987ca8100b gating: change the PassingTestCaseRule string
The first document I went with[1] specified a magic
value containing 'package.test.functional'. I used
that, and my bodhi results[2] looked weird: first,
none of the usual results include 'test.functional';
so, second, there's now a new test.functional line
under 'undefined' in red and with an asterisk next
to it, and another red one without an asterisk.
All four lines seem to link to the same results.

 [1] https://docs.fedoraproject.org/en-US/ci/gating/
 [2] https://bodhi.fedoraproject.org/updates/FEDORA-2019-144ed359e9

A different document[3] specifies a magic value that
more closely conforms to the ones already shown
in the 'undefined' section of older bodhi runs.
That's what I'm trying now.

 [3] https://docs.fedoraproject.org/en-US/rawhide-gating/optin/

Unfortunately neither document has a timestamp so it's
impossible to know which (if any) is up-to-date and/or
correct.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-08-15 13:55:44 -06:00
Ed Santiago
3537282ceb Enable gating tests on rawhide
Purpose: prevent a build from being pushed to stable
unless tests/tests.yml pass; require manual override
on failure.

Counterargument: this is going to fail effective now.
Rawhide has been highly unstable, with kernel and
systemd bugs one right after the other, all preventing
podman tests from passing. (Current blocker: rhbz1740664
in systemd-udev, in which /dev/net/tun is mode 600
which causes slirp4netns to fail).

Countercounterargument: even if all these failures aren't
podman's fault, we still want to catch them and at least
report them early. I am monitoring test runs but I don't
want to be the single point of failure.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-08-14 12:36:23 -06:00