-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define and ship a "testutils" container #1645
Labels
jira
for syncing to jira
Comments
This was referenced Aug 16, 2020
If we did this maybe we could roll the test/functionality from |
cgwalters
added a commit
to cgwalters/rpm-ostree
that referenced
this issue
Mar 11, 2021
Where I stalled out before is this file has `pkg-add foo`, but now that we have the `foo` package pre-built we can move all this stuff into `misc.sh`. I dropped the YAML parsing of `--version` because we don't have python. This is related to coreos/coreos-assembler#1645
cgwalters
added a commit
to coreos/rpm-ostree
that referenced
this issue
Mar 11, 2021
Where I stalled out before is this file has `pkg-add foo`, but now that we have the `foo` package pre-built we can move all this stuff into `misc.sh`. I dropped the YAML parsing of `--version` because we don't have python. This is related to coreos/coreos-assembler#1645
This overlaps a bit with the newly created tracker issue coreos/fedora-coreos-tracker#1639 that @jbtrystram is working on. I'll close this out and we'll track it there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In several of ostree/rpm-ostree external tests we fetch a container image to run privileged for helper utilities, whether that's
python
or a webserver program.This somewhat commonly causes tests to flake; particularly the Fedora registry seems unreliable, but docker.io also has rate limited us in the past. And most of these tests don't otherwise need the internet.
I'd like if as part of coreos-assembler we defined a "test helper" container (perhaps this should be an official FCOS toolbox container) that contains things like a webserver,
strace
, etc.Now what we could do in the qemu-unpriv case is be able to pull this container content over virtio (fs or channel) from the "host" container image and avoid the dependency on networking.
In the non-qemu-unpriv case we'd host this image at a public registry somewhere. But if we eventually wanted to support "offline" tests even in cloud, we'd need to provision a mirror of testutils in the environment.
The text was updated successfully, but these errors were encountered: