Update coverage to 7.15.0 (supersedes #876)#885
Open
javihern98 wants to merge 4 commits into
Open
Conversation
Supersedes Dependabot PR #876, whose lock regeneration dropped the marker-split numpy 2.4.6 entry (dependabot/dependabot-core#5862), collapsing numpy to 2.2.6 for all Python versions. numpy 2.2.6 has no cp314 support, so every pytest-xdist worker crashed with an access violation while importing numpy on windows/3.14.
The split constraint guards Poetry regenerations, but Dependabot's updater (dependabot/dependabot-core#5862) writes a lock that violates the markers, so Dependabot lock diffs still need manual review.
javihern98
marked this pull request as ready for review
July 9, 2026 14:29
javihern98
enabled auto-merge (squash)
July 13, 2026 15:11
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.
Summary
Bumps
coverage7.14.3 → 7.15.0 (dev group floor raised to>=7.15.0,<8.0), with the lock regenerated by Poetry itself. This supersedes Dependabot PR #876, which cannot be merged as-is: its machine-generatedpoetry.lockis invalid.Why #876 fails CI — the
testing (windows-latest, 3.14)job dies withxdist: maximum crashed workers reached. The crash has nothing to do with coverage, pytest-cov, or pytest-xdist:numpy 2.4.6entry and stripped thepython_version == "3.10"marker from thenumpy 2.2.6entry, collapsing numpy to 2.2.6 for all Python versions — violating thenumpy>=2.4.4,<2.5; python_version >= '3.11'constraint introduced in Pin numpy>=2.4.4 for Python >=3.11 so lock regenerations keep cp314 wheels #871. This is the known Dependabot bug dependabot-core#5862 (Poetry multiple-constraint dependencies broken by unrelated updates: only the first lock entry is kept).Windows fatal exception: access violationinsidenumpy._core._multiarray_umathimport during collection, killing all 20 xdist workers instantly (node down: Not properly terminated). On ubuntu/macos 3.14 the 2.2.6 binary happens to import, so only the Windows job failed.In this PR the lock diff touches only coverage; both numpy entries survive with their markers intact.
Checklist
ruff format,ruff check,mypy)pytest) — full suite in CI;tests/APIsmoke run locally with-n auto --cov=vtlengine(239 passed)Impact / Risk
Notes
pyproject.tomlmarkers, andpoetry installtrusts the lock. Any future Dependabot PR here needs its lock diff checked for the numpy entries (or a CI guard added; happy to file a follow-up Task for that).