unit test failure in isolated venv

[yaswant]

Recent changes in #575 to include support for Python 3.14 is successfully running vi CI, but it is failing in an isolated virtual environment.

uv sync --all-extras --python 3.14
uv run python -m pytest --cov=fab tests/unit_tests

stack trace:
fab-unit_test.log

[hiker]

I can't reproduce this, the tests work for me. I am not using uv, so I am not sure if this could have an impact? One thing I noticed is that the log files contains around 7 errors related to files not being found:

E       FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/pytest-of-<user>/pytest-2/test_workspace0/new_workspace/root_symbol_does_not_exit-default-profile-some_Fortran_compiler/metrics/root_symbol_does_not_exit-default-profile-some_Fortran_compiler/metrics.json'

This directory does also not exist for me, but I don't get a failure (I noticed that one warning is still raised during testing. Typically, the missing metrics are expected, and the warnings are explicitly ignored).

I am also surprised seeing <user> in the path, I have an explicit name. Is this just information hiding? Or is that really the path? Could the special characters cause a problem?

I wonder if the problem might be related to matplotlib being installed or not (if all failures are related to metrics). TBH, I think this needs to be debugged by someone who can reproduce this issue, there is too much guessing from my side :(

[hiker]

I am getting some odd errors as well, might be related to mixing 3.10 and 3.14?? In some cases the detection of running in pytest is not working as expected (I am on a branch, but I can't see the changes here affecting this), meaning the faked processes do not work as expected.

It might be worth testing if the following patch changes the behavour?

diff --git a/source/fab/build_config.py b/source/fab/build_config.py
index 1cebe4c..dac9d52 100644
--- a/source/fab/build_config.py
+++ b/source/fab/build_config.py
@@ -129,7 +129,7 @@ class BuildConfig():
         # turn off multiprocessing when debugging
         # todo: turn off multiprocessing when running tests, as a good test
         # runner will run using mp
-        if 'pydevd' in str(sys.gettrace()):
+        if "PYTEST_CURRENT_TEST" in os.environ:
             logger.info('debugger detected, running without multiprocessing')
             self.multiprocessing = False

[yaswant]

I can't reproduce this, the tests work for me. I am not using uv, so I am not sure if this could have an impact? One thing I noticed is that the log files contains around 7 errors related to files not being found:

E       FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/pytest-of-<user>/pytest-2/test_workspace0/new_workspace/root_symbol_does_not_exit-default-profile-some_Fortran_compiler/metrics/root_symbol_does_not_exit-default-profile-some_Fortran_compiler/metrics.json'

This directory does also not exist for me, but I don't get a failure (I noticed that one warning is still raised during testing. Typically, the missing metrics are expected, and the warnings are explicitly ignored).

I am also surprised seeing <user> in the path, I have an explicit name. Is this just information hiding? Or is that really the path? Could the special characters cause a problem?

thanks for looking into this Joerg Henrichs (@hiker). Forgot to mention that I've deliberately masked the username and paths that you see within in <angle-brackets>.

I wonder if the problem might be related to matplotlib being installed or not (if all failures are related to metrics). TBH, I think this needs to be debugged by someone who can reproduce this issue, there is too much guessing from my side :(

Yes, matplotlib-3.11 is installed in the environment.