aio-libs / multidict / 37929202180

86%

Build Type

push

github

Committed by web-flow

Commit Message

Trim the test run of the emulated wheel jobs (#1762)

<!-- Thank you for your contribution! -->

## What do these changes do?

The third `v7.1.0` tag run passed every job except the manylinux riscv64
wheel build, which hit its 120 minute timeout on the last of its eight
wheels; all wheels it built passed their tests. The job took 72 minutes
for 7.0.0: the suite grew from about 2650 to about 4090 tests since
then, and under QEMU each wheel's test run went from about 3.5 to about
8 minutes.

Measured under QEMU on the riscv64 cp314 wheel, two thirds of the time
in the slow tests was the pure-Python parametrization, mostly
large-table tests and the benchmark tests, and most of the rest was a
handful of threaded tests. The pure-Python backend gives the same result
whichever wheel is under test, and native jobs, 32-bit i686 included,
keep running all of it.

This adds four markers: `pure_python` on the pure-Python parametrization
(mirroring `c_extension`), `gil_build` on every test of a GIL build,
`expensive` on 11 large-table tests and `test_multidict_benchmarks.py`,
and `threaded` on the 9 slowest threaded tests. The odd-arch wheel jobs
that run under QEMU add `not (pure_python and expensive) and not
(gil_build and threaded)` to the test command. FT wheels keep every
threaded test, GIL wheels keep the other threaded tests (48 of 61 test
items), and native jobs, aarch64 included, run everything as before.

The changelog entry goes into the unpublished 7.1.0 section, since the
tag gets moved to this merge commit.

## Are there changes in behavior for the user?

No.

## Is it a substantial burden for the maintainers to support this?

No; a new test that is slow under emulation needs one of the two
markers.

## Related issue number

Follow-up to #1760. Failed run:
https://github.com/aio-libs/multidict/actions/runs/37838988742

## Checklist

- [x] I think the code is well written
- [ ] Unit tests for the changes exist N/A, test selection change;
verified as d... (continued)

Coverage Stats

832 of 1664 branches covered (50.0%)

Branch coverage included in aggregate %.

35 of 35 new or added lines in 7 files covered. (100.0%)

1 existing line in 1 file now uncovered.

9740 of 10622 relevant lines covered (91.7%)

1.83 hits per line