Draft
Stabilize scheduled CI by pinning coverage to 7.15.0 across test environments#657
Conversation
Copilot
AI
changed the title
Pin coverage to 7.15.0 to stabilize CI test jobs
Stabilize scheduled CI by pinning coverage to 7.15.0 across test environments
Aug 3, 2026
Copilot created this pull request from a session on behalf of
pancetta
August 3, 2026 07:07
View session
Coverage report
This PR does not seem to contain any modification to coverable code. |
Copilot stopped work on behalf of
pancetta due to an error
August 3, 2026 09:02
The `concurrency = ['multiprocessing']` setting in [tool.coverage.run] causes coverage to install subprocess tracking hooks via its multiprocessing plugin. Newer coverage versions (post 7.15.0) have a regression in this plugin that sends SIGTERM to the tracked process, manifesting as exit code 143 in CI jobs (RayleighBenard, StroemungsRaum, DAE, fenics, mpi4py). Removing `[toml]` from `coverage[toml]` in environment files only prevents the TOML config from being read on Python 3.10; on Python 3.11+ the stdlib tomllib is used automatically, so the multiprocessing plugin remains active. This commit removes the setting from pyproject.toml directly, disabling the plugin on all Python versions.
…st MPI subprocesses
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.
Recent scheduled CI runs on
masterstarted failing in unrelated test jobs (Monodomain,parallelSDC,SDC_showdown) with abrupt process termination (exit 143/15) immediately after pytest startup. The common change across passing vs failing runs wascoveragedrifting from7.15.0to newer builds.Root-cause containment: lock shared test instrumentation dependency
coverageto7.15.0in shared test env:etc/environment-tests.ymlcoverageto7.15.0in Monodomain env:pySDC/projects/Monodomain/etc/environment-monodomain.ymlcoverageto7.15.0in postprocess env:etc/environment-postprocess.ymlScope