3.7.rc: some tests fail if build with -D seccomp=true
Does gitlab now default to ENTER = Send, rather then newline?
Possible dup of #315 (closed), #316 (closed), #317 (closed)
On Arch Linux I just started to investigating the test problematic and essentially following @jbicha and build -miners twice:
- to run the tests (without landlock, that is not supported by our build environment)
- to package things up (with landlock)
On enabling the test I suddenly got hit with:
44/86 tracker-miners:extractor+disc-images / psx-game-image-1 ERROR 0.75s exit status 1
79/86 tracker-miners:functional / test_fts_basic ERROR 15.12s exit status 1
85/86 tracker-miners:functional / test_miner_basic ERROR 19.83s exit status 1
At first I thought the first one was #162, but the log said
=================================== 44/86 ====================================
test: tracker-miners:extractor+disc-images / psx-game-image-1
start time: 10:28:59
duration: 0.75s
result: exit status 1
command: TRACKER_FUNCTIONAL_TEST_CONFIG=/build/tracker3-miners/src/check_build/tests/functional-tests/config/configuration.json MALLOC_PERTURB_=7 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 PYTHONPATH=/usr/lib/tracker-3.0/ UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 TRACKER_EXTRACT_DEADLINE=5 /usr/bin/python3 /build/tracker3-miners/src/tracker-miners/tests/functional-tests/test_extractor_generic.py /build/tracker3-miners/src/tracker-miners/tests/functional-tests/data/extractor-content/disc-images/psx-game-image-1.expected.json
----------------------------------- stdout -----------------------------------
# TAP results for GenericExtractionTestCase
not ok 1 sts/data/extractor-content/disc-images/psx-game-image-1.expe (__main__.GenericExtractionTestCase.sts/data/extractor-content/disc-images/psx-game-image-1.expe)
# Traceback (most recent call last):
# File "/usr/lib/python3.11/unittest/case.py", line 57, in testPartExecutor
# yield
# File "/usr/lib/python3.11/unittest/case.py", line 623, in run
# self._callTestMethod(testMethod)
# File "/usr/lib/python3.11/unittest/case.py", line 579, in _callTestMethod
# if method() is not None:
# ^^^^^^^^
# File "/build/tracker3-miners/src/tracker-miners/tests/functional-tests/test_extractor_generic.py", line 101, in generic_test_extraction
# jsonld = fixtures.get_tracker_extract_output(
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# File "/build/tracker3-miners/src/tracker-miners/tests/functional-tests/fixtures.py", line 465, in get_tracker_extract_output
# raise RuntimeError(
# RuntimeError: tracker-extract didn't return any data.
# Error output was: (tracker-extract-3:5181): GLib-GIO-WARNING **: 11:28:59.739: Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
# 7: syntax error
# file:///build/tracker3-miners/src/tracker-miners/tests/functional-tests/data/extractor-content/disc-images/psx-game-image-1.cue: No metadata or extractor modules found to handle this file
1..1
----------------------------------- stderr -----------------------------------
(test program exited with status code 1)
==============================================================================
And this Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
is also true for the other 2. So I set -D seccomp=false for the tests and everything was fine. Could this be because of some disallowed/restricted syscall?
Here are the check as well as the meson testlog:
Edited by Fabian Bornschein