Merge master into feature/pytest-plugin-issue-70

Brings in the non-ASCII path fix (#1087), the get_ipython() Optional
guard (#1088), and the free-threaded CI setup fix (#1089).

Author: emeryberger

.github/workflows/tests.yml

@@ -87,7 +87,15 @@ jobs:
 
     - name: install test dependencies
       run: |
-        python3 -m pip install pytest pytest-asyncio hypothesis
+        python3 -m pip install pytest pytest-asyncio
+        # hypothesis ships no wheel for free-threaded CPython 3.13, and
+        # building it from source fails there: its dependency chain pulls
+        # pyo3-ffi, and "PyO3 does not support the free-threaded build of
+        # CPython versions below 3.14". That aborted this step under
+        # ``bash -e``, so the 3.13t jobs never reached ``run tests`` at all.
+        # Install it best-effort; the two modules that need it call
+        # pytest.importorskip("hypothesis") and skip when it's absent.
+        python3 -m pip install hypothesis || echo "hypothesis unavailable; property-based tests will skip"
         # torch/JAX/TensorFlow may not be available on free-threaded Python builds
         python3 -m pip install torch --index-url https://download.pytorch.org/whl/cpu || true
         python3 -m pip install -e ".[test]" || python3 -m pip install -e .
@@ -97,7 +105,14 @@ jobs:
       run: |
         ulimit -c unlimited
         echo '/tmp/core.%e.%p' | sudo tee /proc/sys/kernel/core_pattern
-        sudo apt-get install -y gdb
+        # ``apt-get update`` first: the runner image ships a package index
+        # that can be older than the mirror's contents, and installing gdb
+        # then 404s on a superseded libc6-dbg. That failed the whole step
+        # (exit 100), skipping ``run tests`` on 3.14t. gdb is only used by
+        # the optional "Collect crash backtraces" step, so never let its
+        # absence stop the job.
+        sudo apt-get update || true
+        sudo apt-get install -y gdb || echo "gdb unavailable; crash backtraces will be skipped"
 
     - name: Quick memory profiling smoke test
       if: runner.os == 'Linux' && endsWith(matrix.python, 't')
@@ -113,6 +128,12 @@ jobs:
     - name: run tests
       # Free-threaded Python support is experimental; don't block CI on failures
       continue-on-error: ${{ endsWith(matrix.python, 't') }}
+      # SCALENE_TEST_DIAG=1 makes tests/conftest.py print each skip's reason
+      # live and flushed. On free-threaded builds the 45-min job timeout can
+      # cancel pytest before its -rs summary, so this keeps skip reasons in
+      # the log for future debugging.
+      env:
+        SCALENE_TEST_DIAG: ${{ endsWith(matrix.python, 't') && '1' || '' }}
       run: |
         python3 -m pytest
 
@@ -145,8 +166,15 @@ jobs:
     - name: Free-threaded parity test
       # Runs on ALL matrix entries to verify CPU+memory profiling with
       # native code and threads produces comparable results everywhere.
+      #
+      # continue-on-error on ALL jobs (not just t-builds): the contention-ratio
+      # check (8T/1T slowdown <= 3x) is a wall-clock timing assertion, so on a
+      # noisy shared CI runner it spikes past the threshold (observed 3.1x-5.2x)
+      # for reasons unrelated to Scalene. Combined with fail-fast, one such
+      # spike cancelled the whole matrix. The step still runs and prints its
+      # results for inspection; it just no longer fails the job.
       if: runner.os != 'Windows'
-      continue-on-error: ${{ endsWith(matrix.python, 't') }}
+      continue-on-error: true
       run: |
         python3 test/test_freethreaded_parity.py
 
@@ -158,3 +186,46 @@ jobs:
           echo "=== Backtrace from $core ==="
           gdb -batch -ex "thread apply all bt full" python3 "$core" 2>/dev/null || true
         done
+
+  # Windows is profiled via threads, not signals, so the signal-based
+  # interruption that breaks blocking syscalls on Linux (issue #1060) cannot
+  # happen here. This job runs the Windows side of tests/test_eintr_retry.py --
+  # a positive check that profiling a blocking TCP round-trip under
+  # ``scalene run`` completes cleanly -- guarding against any regression that
+  # would reintroduce signal-style interruption on Windows. It is a separate,
+  # scoped job rather than a matrix entry because the full pytest suite is not
+  # yet Windows-clean (Windows support is partial).
+  run-tests-windows:
+    runs-on: windows-latest
+    timeout-minutes: 30
+    strategy:
+      fail-fast: false
+      matrix:
+        python: [ '3.11', '3.13' ]
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: ${{ matrix.python }}
+        cache: pip
+        cache-dependency-path: |
+          requirements.txt
+          pyproject.toml
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        python -m pip install -r requirements.txt
+        python -m pip install numpy
+
+    - name: Build scalene
+      run: pip -v install -e .
+
+    - name: Install test dependencies
+      run: python -m pip install pytest pytest-asyncio hypothesis
+
+    - name: Run Windows profiling test
+      run: python -m pytest tests/test_eintr_retry.py -v