toolbox/playbooks/unit-test.yaml

---
- hosts: all
  tasks:
    - include_tasks: build.yaml

    - name: Test
      command: meson test -C builddir
      args:
        chdir: '{{ zuul.project.src_dir }}'
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68 2019-09-03 13:31:38 +00:00			`---`
			`- hosts: all`
			`tasks:`
playbooks: Highlight failures from 'meson compile' and 'meson install' Currently, 'meson compile' and 'meson install' were being invoked from pre-run playbooks. This meant that a genuine build failure from either of those commands would be shown as a RETRY_LIMIT failure by the CI. This was misleading. It made it look as if the failure was caused by some transient networking problem or that the CI node was too slow due to momentary heavy load, whereas the failure was actually due to a problem in the Toolbx sources. A genuine problem in the sources should be reflected as a FAILURE, not RETRY_LIMIT. However, it's worth noting that 'meson compile' invokes 'go build', which downloads all the Go modules required by the Toolbx sources. This is worth retaining in the pre-run playbooks since it primarily depends on Internet infrastructure beyond the Toolbx sources. As a nice side-effect, the CI no longer gets mysteriously stuck like this while the Go modules are being downloaded: TASK [Build Toolbox] ci-node-36 \| ninja: Entering directory `/home/zuul-worker/src/github.com/containers/toolbox/builddir' ... ci-node-36 \| [8/13] Generating doc/toolbox-rmi.1 with a custom command ci-node-36 \| [9/13] Generating doc/toolbox-run.1 with a custom command ci-node-36 \| [10/13] Generating doc/toolbox.conf.5 with a custom command ci-node-36 \| [11/13] Generating src/toolbox with a custom command https://github.com/containers/toolbox/pull/1158 2022-11-15 23:44:32 +00:00			`- include_tasks: build.yaml`

Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68 2019-09-03 13:31:38 +00:00			`- name: Test`
playbooks: Use the same commands as mentioned in the documentation ... at https://containertoolbx.org/install/ There are some minor benefits to always invoking meson(1), as opposed to directly invoking the underlying build backend, like 'ninja'. It's one less command to be aware of. Secondly, in theory, Meson can be used with backends other than Ninja (see 'meson configure'), even though Ninja is the most likely option for building Toolbx because it's only supported on Linux. https://github.com/containers/toolbox/pull/1142 2022-10-21 18:00:08 +00:00			`command: meson test -C builddir`
Enable Zuul This adds several .yaml files that specify jobs (those in folder playbooks) and one that serves as the main config (.zuul.yaml). Tests and builds are currently executed on every change in PRs (ie., check and gating) and periodically (according to the documentation this pipeline should be run at least once a day). There are 4 tests in total: 1. 'ninja test' - does the same thing that Travis did 2. Fedora 30 - runs the system tests with current Podman and Toolbox in Fedora 30 3. Fedora 31 - the same but for Fedora 31 4. Fedora Rawhide - the same but for Fedora Rawhide https://github.com/containers/toolbox/issues/68 2019-09-03 13:31:38 +00:00			`args:`
			`chdir: '{{ zuul.project.src_dir }}'`