Closed juliangilbey closed 6 months ago
Oops, I forgot the attachment (the full autopkgtest log). pytest-order.log.txt
Can you please check if you get the same problem with pytest 8.1? And if yes, with pytest 7?
There was a problem in pytest 8.0.2 with tests in the CI, but that should have only affected tests under Windows... but the effect was similar - tests have been collected from other locations that where symlinked to the test dir.
Yes, we get the same problem with pytest 8.1.1, but not with pytest 7.4.4; that's the only change I made to the test environment. Hmm.
I suggest you pin pytest to 7 until the issue has been understood and fixed. I assume it's something in the collection process of pytest, or maybe I'm doing something wrong in the tests that is triggered by the pytest change. I won't probably be able to investigate this soon (I will have have next to no free time this week, and will be away the week after), but I'll certainly have a look.
CC @nicoddemus
Thanks @mrbean-bremen! We can't pin to pytest 7, unfortunately, but we can skip the test for now.
It seems that it's this bug in pytest: https://github.com/pytest-dev/pytest/issues/11781 I haven't yet had a chance to find a way to work around this; I'll let you know when I have.
A new bugfix release is out.
A bizarre error, which you may have some insight into. I obtain the same error if I use 1.2.0 or the current HEAD (commit a568bb1):
(A full log is attached, in case it is helpful.)
The tests are called as
python3.12 -m pytest tests perf_tests
in a directory only containing copies ofperf_tests
andtests
.If you have any idea what might be causing this, I'd be very grateful! It doesn't seem to make any sense that something should be looking in this systemd-private directory.