Skip to content

Conversation

@neutrinoceros
Copy link
Contributor

There are several warnings popping up in test sessions, some of which indicating future behavior change in dependencies that could be handled. Turning them into hard failures in CI is a first step towards future proofing and ensures that no new warnings are introduced silently.

@codecov-commenter
Copy link

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 23.69%. Comparing base (3373f93) to head (3b28b2b).
⚠️ Report is 25 commits behind head on master.

Files with missing lines Patch % Lines
vip_hci/fm/negfc_simplex.py 0.00% 1 Missing ⚠️
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #678       +/-   ##
===========================================
- Coverage   62.28%   23.69%   -38.59%     
===========================================
  Files          11       87       +76     
  Lines         928    16835    +15907     
===========================================
+ Hits          578     3989     +3411     
- Misses        350    12846    +12496     

☔ 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.

@neutrinoceros neutrinoceros force-pushed the tst/error-on-warning branch 3 times, most recently from 3405c82 to 0f8b672 Compare August 6, 2025 13:34
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