c/mirror_zfs
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_zfs.git synced 2025-01-31 20:34:22 +03:00
Code Issues Packages Projects Releases Wiki Activity
a44a15d318
mirror_zfs/.github/workflows/scripts
History
Brian Behlendorf ad739614cc CI: Add logs to zloop workflow 
On failure attempt to include the most relevant portions of the
ztest logs in the CI output.  This full logs are still available
for download but often a backtrace and the last output is enough.

Install libunwind to improve the odds of a useful backtrace.

Reviewed-by: Tino Reichardt <milky-zfs@mcmilk.de>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #16573
2024-11-04 11:09:09 -08:00
..
generate-ci-type.py CI: run only sanity check on limited OSes for nonbehavioral changes 2024-11-04 11:08:44 -08:00
merge_summary.awk ZTS: Use QEMU for tests on Linux and FreeBSD 2024-11-04 11:06:02 -08:00
qemu-1-setup.sh ZTS: Use QEMU for tests on Linux and FreeBSD 2024-11-04 11:06:02 -08:00
qemu-2-start.sh ZTS: Use QEMU for tests on Linux and FreeBSD 2024-11-04 11:06:02 -08:00
qemu-3-deps.sh CI: Add logs to zloop workflow 2024-11-04 11:09:09 -08:00
qemu-4-build.sh ZTS: Use QEMU for tests on Linux and FreeBSD 2024-11-04 11:06:02 -08:00
qemu-5-setup.sh ZTS: Use QEMU for tests on Linux and FreeBSD 2024-11-04 11:06:02 -08:00
qemu-6-tests.sh CI: run only sanity check on limited OSes for nonbehavioral changes 2024-11-04 11:08:44 -08:00
qemu-7-prepare.sh ZTS: Fix Summary Page 2024-11-04 11:07:29 -08:00
qemu-8-summary.sh ZTS: Fix Test Summary page generation 2024-11-04 11:06:56 -08:00
qemu-9-summary-page.sh ZTS: Fix Summary Page 2024-11-04 11:07:29 -08:00
README.md ZTS: Use QEMU for tests on Linux and FreeBSD 2024-11-04 11:06:02 -08:00

README.md

Workflow for each operating system:

  • install qemu on the github runner
  • download current cloud image of operating system
  • start and init that image via cloud-init
  • install dependencies and poweroff system
  • start system and build openzfs and then poweroff again
  • clone build system and start 2 instances of it
  • run functional testings and complete in around 3h
  • when tests are done, do some logfile preparing
  • show detailed results for each system
  • in the end, generate the job summary

/TR 14.09.2024