There's a nasty bug in the CI infrastructure: reboots
hang forever[1]. Sometimes they work, but only 25% of
the time -- the rest of the time, gating tests fail.
[1] https://redhat.service-now.com/surl.do?n=PNT0808530
So, let's just disable the reboot and all cgroups v1 tests.
For now, I've disabled with a quick edit that should allow
us to reenable if/when the reboot bug is fixed.
TODO: reevaluate in three months (2020-08). If the reboot
bug is not fixed by then, just scrap the entire cgroups
refactoring and go back to plain standard-test-basic.
Signed-off-by: Ed Santiago <santiago@redhat.com>
The Gating spec[1] used to recommend having one type of
YAML stanza for master, one for released branches. We
just discovered today that this breaks when master
forks into a release branch: the string 'stable'
needs to be manually changed to 'testing', and
nobody is going to remember to do that, and I can't
think of a (non-tedious) way to add automated checks.
As of 2019-08 (09d7d4f), though, the Gating spec suggests
having *both* stanzas together in the same gating.yaml
file. @pingou himself concurs[2]. Although this is
horrible duplication -- two hundred characters, repeated
with only six of those different -- it seems cleaner
than the maintenance burden of having to update
release branches.
[1] https://docs.fedoraproject.org/en-US/ci/gating/
[2] https://src.fedoraproject.org/rpms/podman/pull-request/33
Oh, also, add a new 'subject_type' line apparently "required"
even though things seem to have been working fine without it.
(Source: same commit, 09d7d4f, on gating.adoc).
Signed-off-by: Ed Santiago <santiago@redhat.com>
Looks like the code I copied from standard-test-roles
has changed; let's reincorporate it.
In particular, there is now an annoying step that pulls
logs and artifacts from remote-host:/tmp/artifacts .
Well, that doesn't exist in our case because /tmp may
not survive reboots. Workaround: after completion of
each test, push our local (master) artifacts to remote.
And, fix a typo in results.yml
Signed-off-by: Ed Santiago <santiago@redhat.com>
DO NOT COMMIT.
I'm simply trying to understand why reboot is failing.
This commit adds some debug statements to try to get
a sense for what grubenv looks like.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Gating tests are still failing. Actually, the BATS portion is
all passing, it just seems to be the end part (infrastructure)
that fails. Let's try creating a results.yml file.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Podman gating tests failed:
... back_again.changed): 'dict object' has no attribute 'changed'
Previous error (ignored) was a timeout in the reboot step. I have
no idea how to fix this, so let's try putting the reboot and wait
steps into a 'block' section and removing the '.changed'.
Tested with 1minutetip. Seems to work, but the reboot was quick
so it didn't trigger the same code.
Signed-off-by: Ed Santiago <santiago@redhat.com>
