test_sequential: resolve() the system_executable (#2751)

When the _base_executable is a hardlink (macOS homebrew), then the virtualenv `PythonInfo.current_system()` call might not return the same path as tox's PythonInfo.interpreter, even though they would be pointing to the same file. fix issue #2720
tox-dev · Dec 19, 2022 · 9972a82 · 9972a82
1 parent 968ea7d
commit 9972a82
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/docs/changelog/2720.bugfix.rst b/docs/changelog/2720.bugfix.rst
@@ -0,0 +1,2 @@
+Fix assertion in ``test_result_json_sequential`` when interpreter
+``_base_executable`` is a hardlink (macOS homebrew) - by user:`masenf`
diff --git a/tests/session/cmd/test_sequential.py b/tests/session/cmd/test_sequential.py
@@ -70,7 +70,7 @@ def test_result_json_sequential(
 
     py_info = PythonInfo.current_system()
     host_python = {
-        "executable": py_info.system_executable,
+        "executable": str(Path(py_info.system_executable).resolve()),
         "extra_version_info": None,
         "implementation": py_info.implementation,
         "is_64": py_info.architecture == 64,