Skip to content

Run python tests after changes to codecov.yml #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2024

Conversation

ogenstad
Copy link
Contributor

Seems like we need to have this in place for codecov to pick up changes to the config as it gets triggered when we ping codecov after the tests have run.

@github-actions github-actions bot added the group/ci Issue related to the CI pipeline label Oct 14, 2024
Copy link

codecov bot commented Oct 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

@@           Coverage Diff            @@
##           develop      #75   +/-   ##
========================================
  Coverage    43.07%   43.07%           
========================================
  Files           70       70           
  Lines         6653     6653           
  Branches      1307     1307           
========================================
  Hits          2866     2866           
- Misses        3458     3518   +60     
+ Partials       329      269   -60     
Flag Coverage Δ
python-3.10 43.07% <ø> (ø)
python-3.11 43.07% <ø> (ø)
python-3.12 43.07% <ø> (ø)
python-3.9 43.01% <ø> (ø)

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

see 4 files with indirect coverage changes

@ogenstad ogenstad marked this pull request as ready for review October 14, 2024 07:30
@ogenstad ogenstad merged commit 472d01c into develop Oct 14, 2024
12 checks passed
@ogenstad ogenstad deleted the pog-run-python-tests-after-coverage-change branch October 14, 2024 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
group/ci Issue related to the CI pipeline
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants