Three tests in XCP-D's test suite use with pytest.warns to detect raised warnings. For some reason, these are successfully captured on the standard CI runs (i.e., within the PR, then on main), but are not for the release CI runs.
Additional details
xcp_d version: 0.7.1rc1 - 0.7.1rc2
Docker version:
Singularity version:
What actually happened?
FAILED xcp_d/tests/test_utils_bids.py::test_collect_participants - Failed: DID NOT WARN. No warnings of type (<class 'xcp_d.utils.bids.BIDSWarning'>,) were emitted.
Emitted warnings: [].
FAILED xcp_d/tests/test_utils_confounds.py::test_motion_filtering_lp - Failed: DID NOT WARN. No warnings of type (<class 'Warning'>,) were emitted.
Emitted warnings: [].
FAILED xcp_d/tests/test_utils_confounds.py::test_motion_filtering_notch - Failed: DID NOT WARN. No warnings of type (<class 'UserWarning'>,) were emitted.
Emitted warnings: [ DeprecationWarning('Conversion of an array with ndim > 0 to a scalar is deprecated, and will error in future. Ensure you extract a single element from your array before performing this operation. (Deprecated NumPy 1.25.)')].
Summary
Three tests in XCP-D's test suite use
with pytest.warns
to detect raised warnings. For some reason, these are successfully captured on the standard CI runs (i.e., within the PR, then onmain
), but are not for the release CI runs.Additional details
What actually happened?
Reproducing the bug
I'm not actually sure how to reproduce this.