Skip to content
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

Xfail flaky ontobee tests, unless running daily tests #1423

Merged
merged 2 commits into from
Mar 25, 2024
Merged

Conversation

jwodder
Copy link
Member

@jwodder jwodder commented Mar 22, 2024

Closes #1422.

@jwodder jwodder added the tests Add or improve existing tests label Mar 22, 2024
Copy link

codecov bot commented Mar 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.11%. Comparing base (21ef19d) to head (6e33659).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1423      +/-   ##
==========================================
+ Coverage   67.96%   68.11%   +0.15%     
==========================================
  Files          77       77              
  Lines       10523    10529       +6     
==========================================
+ Hits         7152     7172      +20     
+ Misses       3371     3357      -14     
Flag Coverage Δ
unittests 68.11% <100.00%> (+0.15%) ⬆️

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.

@jwodder jwodder marked this pull request as ready for review March 22, 2024 17:43
reason="Flaky ontobee site",
strict=False,
raises=requests.RequestException,
)
Copy link
Member

Choose a reason for hiding this comment

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

could you please place this into @mark.xfail_ontobee similarly to @mark.skipif_no_network to avoid duplication/clutter?

Copy link
Member

Choose a reason for hiding this comment

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

@jwodder ping on this one so we could bring our tests back into greenland

Copy link
Member Author

Choose a reason for hiding this comment

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

@yarikoptic The custom mark machinery only seems to support custom skipif decorators, not xfail. I think creating a custom mark.xfail_ontobee would be more trouble than it's worth.

Copy link
Member

Choose a reason for hiding this comment

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

Hmm, ok

What about just binding decorator into a helper "variable" eg @mark_xfail_ontobee or that wouldn't work?

Copy link
Member Author

Choose a reason for hiding this comment

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

It seems to work, but now the tests are failing due to #1424.

Copy link
Member

Choose a reason for hiding this comment

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

ok, since seems to be unrelated -- let's proceed. Thank you @jwodder

@yarikoptic yarikoptic merged commit 74897b4 into master Mar 25, 2024
11 of 28 checks passed
@yarikoptic yarikoptic deleted the gh-1422 branch March 25, 2024 15:45
Copy link

github-actions bot commented May 3, 2024

🚀 PR was released in 0.62.0 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released tests Add or improve existing tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ontobee: mark the tests, allow for that mark to xfail atm
2 participants