CI: Add junit test log artifact
Merge request reports
Activity
added CI label
Additionally meson does not write these logs when the test is run with
-v, given that we do that with some tests, it would not work properly for these.Edited by Marvin Scholzadded 2 commits
- Resolved by Jean-Baptiste Kempf
As the meson bug is fixed, any objections do bumping the meson versions on the images to a recent enough one that includes the fix?
- Last reply by Jean-Baptiste Kempf
mentioned in issue #374 (closed)
added 341 commits
-
6c62ef9a...396122d9 - 340 commits from branch
videolan:master - 50a20bbf - CI: Add junit test log artifact
-
6c62ef9a...396122d9 - 340 commits from branch
- Resolved by Jean-Baptiste Kempf
So, I've been investigating why some jobs' output cannot be read. Turns out it's from
testdata_seek-stress / section5:[...]/build/../tests/dav1d-test-data/8-bit/features/section5.obu is not an IVF file [tag=^R|0x12000a0b]
The important part is the ^R which is apparently invalid XML. This only affects jobs which run seek-stress and not overwrite the log with a newer
meson testrun (eg.test-debian).Not sure what the best course of action would be.
Related: #357
- Last reply by Matthias Dressel
mentioned in merge request dav1d-test-data!88 (merged)
added 19 commits
-
50a20bbf...36beb818 - 18 commits from branch
videolan:master - 64a6ccfa - CI: Add junit test log artifact
-
50a20bbf...36beb818 - 18 commits from branch
added 30 commits
-
64a6ccfa...4a52aa47 - 29 commits from branch
videolan:master - 9f3ab0d0 - CI: Add junit test log artifact
-
64a6ccfa...4a52aa47 - 29 commits from branch
added 2 commits
enabled an automatic merge when the pipeline for f6b66515 succeeds
changed milestone to %1.0.0
