keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
82b27de843
rpm-ostree/.papr.yml

47 lines
1.1 KiB
YAML
Raw Normal View History

Rework vmcheck to use `kola spawn`, move off of PAPR There's a lot going on here, but essentially: 1. We change the `vmcheck` model so that it always operates on an immutable base image. It takes that image and dynamically launches a separate VM for each test using `kola spawn`. This means we can drop a lot of hacks around re-using the same VMs. 2. Following from 1., `vmoverlay` now takes as input a base image, overlays the built rpm-ostree bits, then creates a new base image. Of course, we don't have to do this in CI, because we build FCOS with the freshly built RPMs (so it uses `SKIP_VMOVERLAY=1`). `vmoverlay` then will be more for the developer case where one doesn't want to iterate via `cosa build` to test rpm-ostree changes. I say "will" because the functionality doesn't exist yet; I'd like to enhance `cosa dev-overlay` to do this. (Note `vmsync` should still works just as before too.) 3. `vmcheck` can be run without building the tree first, as `tests/vmcheck.sh`. The `make vmcheck` target still exists though for finger compatibility and better meshing with `vmoverlay` in the developer case. What's really nice about using kola spawn is that it takes care of a lot of things for us, such as the qemu command, journal and console gathering, and SSH. Similarly to the compose testsuites, we're using parallel here to run multiple vmcheck tests at once. (On developer laptops, we cap parallelism at `$(nproc) - 1`).
2019-12-13 20:23:41 +03:00
branches:
- master
- auto
- try
ci: add centos build checker We should make sure that we can build on CentOS 7, so that we don't inadvertently break the rdgo c7 stream. This will be enforced even more explicitly when we were integrate RPM building in PAPR. Closes: #824 Approved by: cgwalters
2017-06-08 23:17:33 +03:00
ci: Bump to f29 Better late than never! Closes: #1787 Approved by: cgwalters
2019-03-15 17:00:52 +03:00
# NB: when bumping 29 here, also bump compose script
compose: use test env fedora.repo file instead During provisioning, PAPR injects a fedora.repo pointing at a much better & faster mirror than dl.fp.o. Let's use that to make the compose test less flaky. Hoping to make these sorts of optimizations more discoverable in upstream PAPR. Closes: #799 Approved by: cgwalters
2017-05-26 23:21:02 +03:00
ci: Bump to f29 Better late than never! Closes: #1787 Approved by: cgwalters
2019-03-15 17:00:52 +03:00
context: f29-compose1
ci: make compose test required This has been around for a while now and has found regressions in the past, so let's make it required. Also rename the contexts to make it clear that what version of Fedora they're running on. Closes: #860 Approved by: cgwalters
2017-07-05 19:01:31 +03:00
tests: Add ./tests/compose Our current compose tests only use a synthetic `empty.rpm`, but this really limits usefulness. Let's make a test suite that requires an internet connection and downloads Fedora RPMs and does "real" tree composes. See the updated `tests/README.md` for more information. This is still a WIP. Closes: #531 Approved by: jlebon
2016-12-03 02:07:08 +03:00
build: false
ci: make compose test required This has been around for a while now and has found regressions in the past, so let's make it required. Also rename the contexts to make it clear that what version of Fedora they're running on. Closes: #860 Approved by: cgwalters
2017-07-05 19:01:31 +03:00
ci: Stop rebasing FAH on updates branch The stable branch should have the updated librpm now. Also bump slightly the compose tests timeout. Closes: #1585 Approved by: jlebon
2018-10-01 20:15:02 +03:00
timeout: 35m
tests: Add ./tests/compose Our current compose tests only use a synthetic `empty.rpm`, but this really limits usefulness. Let's make a test suite that requires an internet connection and downloads Fedora RPMs and does "real" tree composes. See the updated `tests/README.md` for more information. This is still a WIP. Closes: #531 Approved by: jlebon
2016-12-03 02:07:08 +03:00
# This test case wants an "unprivileged container with bubblewrap",
# which we don't have right now; so just provision a VM and do a
# docker --privileged run.
host:
ci: Bump to f29 Better late than never! Closes: #1787 Approved by: cgwalters
2019-03-15 17:00:52 +03:00
distro: fedora/29/atomic
ci/papr: Bump compose tests to 4 min vCPUs Compose is a slow test right now. Down the line what I'd like to do is: https://github.com/projectatomic/papr/pull/70 Since this job can be scheduled as a container, not a VM. There's no reason to grab a whole 8GB of RAM for it, but we *do* want multiple CPUs. Containers do that by default. Closes: #1187 Approved by: jlebon
2018-01-09 18:46:23 +03:00
# Compose tests are slow and should be parallelized
specs:
cpus: 4
tests: Add ./tests/compose Our current compose tests only use a synthetic `empty.rpm`, but this really limits usefulness. Let's make a test suite that requires an internet connection and downloads Fedora RPMs and does "real" tree composes. See the updated `tests/README.md` for more information. This is still a WIP. Closes: #531 Approved by: jlebon
2016-12-03 02:07:08 +03:00
ci: Split compose test into two The `f28-compose` test keeps timing out. Some time recently, I/O performance of the internal OpenStack instance used for testing has degraded. I have a ticket open to investigate the regression though haven't had any luck so far. Let's just take the easy way out and split the test into two testsuites. This is obviously hacky, and sad, and unfortunate. But the PRs must keep flowing until we finally wean off of OpenStack. Closes: #1498 Approved by: cgwalters
2018-08-09 19:14:01 +03:00
env:
RPMOSTREE_COMPOSE_TEST_FILTER: odd
Add releasever opt, avoid opening up host's rpmdb in treecompose Closes: https://github.com/projectatomic/rpm-ostree/issues/546 Previously, we'd open up the host's rpmdb for both `compose tree` and `ex container`. In the first case, because we require root, we'd succeed. For `ex container`, we'd spew an error. Fixing this was trickier than I thought. First because there was *also* a libdnf bug here: https://github.com/rpm-software-management/libdnf/pull/307 Second, there's a compatibility hazard here for anyone using `.repo` files that reference `$releasever`. This actually happened to me with `ex container` as I'd just done a `ln -s /etc/yum.repos.d/fedora.repo rpmmd.repos.d`. I fixed that first by doing a `sed -i -e 's,$releasever,26,' rpmmd.repos.d/*.repo`. As far as I can see today, none of Fedora Atomic or CentOS AH rely on this. But in order to enhance compatibility, let's add a "releasever" option. This makes it easier again to reuse stock `.repo` files if we wanted to do so. (Also, I realized we can just use `/usr/share/empty` as *the* canonical immutable empty directory) Closes: #875 Approved by: jlebon
2017-07-13 19:37:41 +03:00
# Copy yum.repos.d to get any injected repos from the host, which
# will point to a closer mirror. Note we substitute $releasever
# since https://github.com/projectatomic/rpm-ostree/pull/875
tests: Add ./tests/compose Our current compose tests only use a synthetic `empty.rpm`, but this really limits usefulness. Let's make a test suite that requires an internet connection and downloads Fedora RPMs and does "real" tree composes. See the updated `tests/README.md` for more information. This is still a WIP. Closes: #531 Approved by: jlebon
2016-12-03 02:07:08 +03:00
tests:
compose: use test env fedora.repo file instead During provisioning, PAPR injects a fedora.repo pointing at a much better & faster mirror than dl.fp.o. Let's use that to make the compose test less flaky. Hoping to make these sorts of optimizations more discoverable in upstream PAPR. Closes: #799 Approved by: cgwalters
2017-05-26 23:21:02 +03:00
- docker run --privileged --rm
ci: Split compose test into two The `f28-compose` test keeps timing out. Some time recently, I/O performance of the internal OpenStack instance used for testing has degraded. I have a ticket open to investigate the regression though haven't had any luck so far. Let's just take the easy way out and split the test into two testsuites. This is obviously hacky, and sad, and unfortunate. But the PRs must keep flowing until we finally wean off of OpenStack. Closes: #1498 Approved by: cgwalters
2018-08-09 19:14:01 +03:00
-e RPMOSTREE_COMPOSE_TEST_FILTER
Add test infra for `ex container`, and one test for bash We have some unit-style tests that run `ex container`, but they aren't "real"; they don't use scripts for example. Let's add tests for this similar to `tests/compose`. We use a 26 base, but the target repos need to be 27 to pick up the fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1478172 Add some bits to share infra between `tests/compose` and `tests/ex-container`; basically handling the rpmmd repos. I tweaked things to be more streamlined there between the `.papr.yml` and the test script. Right now this is just one test for `bash`, but lays some of the infrastructure for doing more. One thing that we need to do to improve more here is to better cache RPMs, a bit like the compose tests do. Closes: #1024 Approved by: jlebon
2017-09-29 17:01:18 +03:00
-e RPMOSTREE_COMPOSE_TEST_USE_REPOS=/etc/yum.repos.d.host
compose: use test env fedora.repo file instead During provisioning, PAPR injects a fedora.repo pointing at a much better & faster mirror than dl.fp.o. Let's use that to make the compose test less flaky. Hoping to make these sorts of optimizations more discoverable in upstream PAPR. Closes: #799 Approved by: cgwalters
2017-05-26 23:21:02 +03:00
-v /etc/yum.repos.d:/etc/yum.repos.d.host:ro
-v $(pwd):/srv/code -w /srv/code
ci: Bump to f29 Better late than never! Closes: #1787 Approved by: cgwalters
2019-03-15 17:00:52 +03:00
registry.fedoraproject.org/fedora:29 /bin/sh -c
ci/compose: Use host repos for building rpm-ostree too We want to use the host repos not just for downloading the packages we'll compose trees with, but also for the rpm-ostree build itself leading up to the tests. Closes: #1585 Approved by: jlebon
2018-10-01 22:23:25 +03:00
"cp /etc/yum.repos.d.host/* /etc/yum.repos.d/ && ./ci/build.sh && make install && ./tests/compose"
compose-tests: add more tests Add a few more tests to exercise some of the treefile options. We do need to also expand test-basic.sh itself to sanity-check the structure of a normal ostree compose. That's up next on the list. Closes: #548 Approved by: cgwalters
2016-12-09 01:31:20 +03:00
artifacts:
tests: Run compose tests in parallel ∥ Over a year later, the "opening the host rpmdb" bug is fixed, so we can do composes in parallel ∥, hooray! I'm dusting this off since we were running into CI (PAPR) timeouts when I was adding more to the compose tests. Closes: #545 Approved by: jlebon
2018-01-08 22:54:10 +03:00
- test-compose-logs
ci: run the improved-sanity-test Start running the improved-sanity-test from atomic-host-tests to make sure the system works. This is an easy way to get PR-level comprehensive integration tests for free. But note that we *don't* mark it as required since the tests are not stored here and it can happen that they need to be adjusted for new rpm-ostree behaviours. In this way, this added check also allows us to give a heads-up that breaking changes are coming. Closes: #899 Approved by: cgwalters
2017-07-27 21:27:31 +03:00
---
ci: Split compose test into two The `f28-compose` test keeps timing out. Some time recently, I/O performance of the internal OpenStack instance used for testing has degraded. I have a ticket open to investigate the regression though haven't had any luck so far. Let's just take the easy way out and split the test into two testsuites. This is obviously hacky, and sad, and unfortunate. But the PRs must keep flowing until we finally wean off of OpenStack. Closes: #1498 Approved by: cgwalters
2018-08-09 19:14:01 +03:00
inherit: true
ci: Bump to f29 Better late than never! Closes: #1787 Approved by: cgwalters
2019-03-15 17:00:52 +03:00
context: f29-compose2
ci: Split compose test into two The `f28-compose` test keeps timing out. Some time recently, I/O performance of the internal OpenStack instance used for testing has degraded. I have a ticket open to investigate the regression though haven't had any luck so far. Let's just take the easy way out and split the test into two testsuites. This is obviously hacky, and sad, and unfortunate. But the PRs must keep flowing until we finally wean off of OpenStack. Closes: #1498 Approved by: cgwalters
2018-08-09 19:14:01 +03:00
env:
RPMOSTREE_COMPOSE_TEST_FILTER: even
Reference in New Issue Copy Permalink