debian-forge/test/run
Michael Vogt 1278e5d217 test: fix test_assembler to support parallel runs and run in parallel
The `test_assembler.py` hardcods some filesystem and partition
UUIDs. This leads to hard to diagnose test failures when the
test is run in parallel. The btrfs and xfs filesystem drivers
will see the same uuid for multi created images and error sometimes with
someting like:
```
Mar 06 10:22:54 top kernel: BTRFS error: device /dev/loop104 belongs to fsid aff010e9-df95-4f81-be6b-e22317251033, and the fs is already mounted, scanned by mount (123856)
```
Its a race that only happens when two images are checked at the
same time.

This commit fixes the issue by just using a randomized UUID in
the test_assemblers.py. It also re-enables running the test in
parallel (which make it run a lot faster, from 34min to 14min).
2024-03-06 12:28:10 +01:00
..
__init__.py test: '{. -> ./run}/test_sources.py' 2020-04-24 15:50:44 +02:00
test_assemblers.py test: fix test_assembler to support parallel runs and run in parallel 2024-03-06 12:28:10 +01:00
test_boot.py test/run/boot: migrate to a v2 manifest 2023-11-14 10:45:44 -08:00
test_devices.py test: fix all pylint issues 2024-01-02 19:31:31 +01:00
test_executable.py test: fix executable test 2022-02-15 13:25:23 +00:00
test_exports.py test: export schemas in testing_libdir_fixture 2024-01-18 08:44:07 +01:00
test_mount.py test: update test_mount.py for lsblk --json differences 2024-01-16 13:51:30 +01:00
test_noop.py test: fix all pylint issues 2024-01-02 19:31:31 +01:00
test_sources.py test: fix all pylint issues 2024-01-02 19:31:31 +01:00
test_stages.py test/stages: read expected data from manifest 2024-02-21 17:55:37 +01:00