Don't run SSL tests on Windows x86

[A5rocks]

BACKWARDS INCOMPATIBLE: Support for 32-bit Windows has been removed. Users should move to a 64-bit Python installation.

Originally posted by @A5rocks in #3463 (comment)

[yashkuceriya]

Validated a local patch for this and wanted to record the concrete behavior before asking for maintainer direction.

Current baseline on main (0524dc17, rechecked on July 20, 2026):

• Windows CI still schedules arch: x86 jobs in .github/workflows/ci.yml.
• ci.sh still installs test-requirements.txt for those jobs.
• The only Trio test modules that directly depend on the SSL-only stack here are src/trio/_tests/test_ssl.py, src/trio/_tests/test_dtls.py, and src/trio/_tests/test_highlevel_ssl_helpers.py (the last imports fixtures from test_ssl.py).

The narrow patch I validated locally does three things:

• sets SKIP_SSL_TESTS=1 for Windows x86 in the workflow
• filters the direct SSL-only packages (cryptography, pyopenssl, trustme) out of the x86 requirements install in ci.sh
• skips those three SSL-related test modules when that flag is set

Why this seemed like the narrowest fit:

1. It keeps the Windows x86 job covering the rest of Trio instead of dropping the job entirely.
2. It isolates the unsupported SSL/DTLS path without changing x64 Windows coverage.
3. It stays aligned with the issue's stated problem rather than broadening the scope to general 32-bit Windows support.

Closest practical validation I could run locally on July 20, 2026:

• bash -n ci.sh
• YAML parse of .github/workflows/ci.yml
• built the filtered requirements file and confirmed those direct SSL-only packages are removed
• PYTHONPATH=tests /private/tmp/trio-skipssl-venv/bin/python -m pytest -q src/trio/_tests --ignore=src/trio/_tests/test_ssl.py --ignore=src/trio/_tests/test_dtls.py --ignore=src/trio/_tests/test_highlevel_ssl_helpers.py
• result: 450 passed, 58 skipped, 2 xfailed in 6.24s

I haven't opened a PR because I couldn't find a maintainer decision yet on whether the preferred outcome is:

• keep the Windows x86 job and skip the SSL modules, or
• drop Windows x86 coverage more broadly.

If keeping the non-SSL x86 job is the intended direction, I have a small local branch ready and can turn it into a focused PR.

[A5rocks]

Please don't open a PR with an LLM comment, or it will be closed. Thanks! Also I prefer programmatic pytest.skip instead of littering ci.sh. No need to do weird requirements installation -- cryptography installs just fine.