Skip to content

Conversation

@mikemhenry
Copy link
Contributor

Checklist

  • Added a news entry

Developers certificate of origin

@codecov
Copy link

codecov bot commented Feb 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.89%. Comparing base (244e2f9) to head (4246c6a).
Report is 83 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1152      +/-   ##
==========================================
- Coverage   93.53%   91.89%   -1.64%     
==========================================
  Files         142      142              
  Lines       10635    10632       -3     
==========================================
- Hits         9947     9770     -177     
- Misses        688      862     +174     
Flag Coverage Δ
fast-tests 91.89% <ø> (?)
slow-tests ?

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.

Copy link
Contributor

@atravitz atravitz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

go for it

@mikemhenry mikemhenry merged commit 064f33d into main Feb 20, 2025
10 of 11 checks passed
@mikemhenry mikemhenry deleted the fix/flaky-test branch February 20, 2025 21:58
@github-actions
Copy link

No API break detected ✅

@pytest.mark.download
# Sometimes we get a DOI lookup error from duecredit
@pytest.mark.flaky(reruns=3, only_rerun=ValueError, reruns_delay=10)
#@pytest.mark.flaky(reruns=3, only_rerun=ValueError, reruns_delay=10)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to not leave this lying around long term. @mikemhenry or @atravitz could you open an issue to track the removal (or re-addition) of this flaky mark?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure #1161

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.

4 participants