Repository navigation
ci(experimental): give the GraalPy leg room to finish (#2739) - #2741
Merged
Merged
Conversation
On ab7be2f, job 125752017215 lost no GraalPy worker but hit the 110-minute timeout during the rest: its shards took 6386 s, on a runner 1.46-1.86 times slower than #2713's estimates assumed, and tests/protocols/internet and tests/protocols/application ran 11.5 and 13.9 minutes, their largest worker at 2.25 and 2.48 GiB RSS. - Run unit tests: timeout 110m -> 180m, step cap 120 -> 190, job cap 140 -> 210, about 1.5 times the leg's 7110-7340 s there (estimate); Containment summary's timeout warning and 137 threshold follow. - SHARDS: split those two at test_igmp* and test_tls* by that job's JUnit seconds, so no shard but tests/const takes as many. - Pins of the caps and the timeout in tests/project follow; the #1963 and timeout notes in workflows.rst gain the measurements. Collecting the tier through util/pytest_shards.py on CPython gives the same 3058 node ids, none twice, for the old and new SHARDS. tests/project passes, each module in its own process; the moved pins fail on the base workflow.
Owner
Author
|
GOOD TO GO at
|
Contributor
|
Coverage: 94.45% (unit tier, Python 3.15,
Per-file detail: the |
Owner
Author
|
The Experimental run at |
JarryShaw
added a commit
that referenced
this pull request
Nov 3, 2026
- Breaking: a short CALIPSO, SMF_DPD or MPL Opt Data Len raises ProtocolError, where 1.5.x raised FieldValueError, and a cut after the type octet reads short (#2737), a new entry; AppType.__registries__ is an Info, into the #2734 entry (#2735). - Changed: const packages import their enumerations lazily through pcapkit.utilities.lazy.lazy_exports (#2735); the docs extra pins sphinx-autodoc-typehints 3.17.4 (#2742), as 1.5.0 recorded its pin. - Fixed: the dumps keep a field renamed for clashing with an Info builtin name (#2736). - Folded: the GraalPy leg's timeout and shards into the CI-legs entry (#2741); the #2735 and #2737 rulings into the conventions entry. - No entry for the docs-only #2744 and #2746. - 1.6.0's :func:`bytes` role is :class:`bytes`, so the changelog pages build with no nitpicky warning. Old values measured against v1.5.1. - CHANGELOG.md regenerated; util/changelog_md.py --check passes.
1 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
make pylint,make mypy,make isort)make testpasses, and a test case covers the changeWhat is the purpose of your pull request?
ci— workflows or build toolingDescription of your pull request and other information
After #2720 split the long shards, the first uninterrupted GraalPy run on
mainlost no workers. It then timed out at 110 minutes with no test failures: job 125752017215, exit 124, interrupted 224 s into the run over the rest. The 20 split shards took 6386 s on a runner 1.46–1.86× slower than the one the split was sized on.Run unit testsstep: the timeout rises to 180 minutes. The step cap is now 190 and the job cap 210, keeping the old gaps. The SIGKILL threshold and the warning text follow. The projected leg is about 7110–7340 s, so this leaves about 1.5× headroom.SHARDS: the two slowest shards are split again, sized from that job's JUnit seconds.tests/protocols/internetgainstest_igmp*(693 s in that job) andtests/protocols/applicationgainstest_tls*(835 s). Every test still runs exactly once: a CPython collection gives the same node-id set for the old and newSHARDS.tests/projectand the test: sort the remaining GraalPy-only failures into defects and gates #1963 note inworkflows.rstmatch.Closes #2739