Skip to content

Conversation

sschuberth
Copy link
Member

@sschuberth sschuberth commented Mar 25, 2025

See 1. This requires several updates to expected test results which have been manually verified to be actually correct (in the context of the documented work-around applied).

Copy link

codecov bot commented Mar 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.78%. Comparing base (034d082) to head (939a47a).
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #10088      +/-   ##
============================================
+ Coverage     56.76%   56.78%   +0.01%     
  Complexity     1640     1640              
============================================
  Files           337      337              
  Lines         12469    12472       +3     
  Branches       1172     1172              
============================================
+ Hits           7078     7082       +4     
+ Misses         4940     4939       -1     
  Partials        451      451              
Flag Coverage Δ
funTest-docker 71.03% <100.00%> (+0.08%) ⬆️
funTest-non-docker 33.02% <ø> (ø)
test-ubuntu-24.04 41.06% <0.00%> (-0.02%) ⬇️
test-windows-2022 41.04% <0.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sschuberth
Copy link
Member Author

sschuberth commented Mar 25, 2025

I've locally verified that running LC_ALL=C ./gradlew -p plugins/package-managers/python/ funTest test passes except for those PipenvFunTests blocked by aboutcode-org/python-inspector#173. However, the latter already has aboutcode-org/python-inspector#201 available.

@sschuberth sschuberth changed the title deps(docker): Upgrade python-inspector to version 0.13.1 deps(docker): Upgrade python-inspector to version 0.14.0 Jun 4, 2025
@sschuberth sschuberth force-pushed the pi-upgrade branch 2 times, most recently from fa5b354 to d8337ae Compare June 4, 2025 18:14
@sschuberth sschuberth marked this pull request as ready for review June 4, 2025 18:16
@sschuberth sschuberth requested a review from a team as a code owner June 4, 2025 18:16
@sschuberth sschuberth enabled auto-merge (rebase) June 4, 2025 18:16
See [1]. This requires several updates to expected test results which
have been manually verified to be actually correct (in the context of the
documented work-around applied).

[1]: https://github.com/aboutcode-org/python-inspector/releases/tag/v0.14.0

Signed-off-by: Sebastian Schuberth <[email protected]>
@sschuberth sschuberth merged commit 142effc into main Jun 4, 2025
26 checks passed
@sschuberth sschuberth deleted the pi-upgrade branch June 4, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants