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

Let flaky adaptive tests be rerun #9043

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

berland
Copy link
Contributor

@berland berland commented Oct 25, 2024

These adaptive localization tests fail very often on weak hardware, and is hampering the deploy process.

Adding reruns on failure will lead to similar hampering when the test actually starts to fail for the correct reasons, but this we have to live with.

Issue
Resolves pain by 🩹 (#8787)

Approach
♻️

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Create Backport PR to latest release

These adaptive localization tests fail very often on weak
hardware, and is hampering the deploy process.

Adding reruns on failure will lead to similar hampering when
the test actually starts to fail for the correct reasons, but this
we have to live with.
@berland berland self-assigned this Oct 25, 2024
@berland berland added the release-notes:flaky-test-fix PR fixes a flaky test label Oct 25, 2024
@eivindjahren
Copy link
Contributor

I think we would have to check whether this works, by rerunning the actions until we observe a retry. Currently the tests timeout at 600s. If the failure mechanism (seems to be some sort of connection problem) would propagate to a failure immediately rather than a deadlock, then that would also help.

Copy link
Contributor

@eivindjahren eivindjahren left a comment

Choose a reason for hiding this comment

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

I think if we can show that the test is retried or that this makes the workflow more stable then we can merge the PR. Mind, #8787 should be high priority as clearly something is really wrong on mac.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.84%. Comparing base (e4445c2) to head (ebf10f1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9043      +/-   ##
==========================================
+ Coverage   90.81%   90.84%   +0.03%     
==========================================
  Files         352      352              
  Lines       21746    21746              
==========================================
+ Hits        19749    19756       +7     
+ Misses       1997     1990       -7     
Flag Coverage Δ
cli-tests 39.02% <ø> (+0.05%) ⬆️
gui-tests 72.57% <ø> (-0.01%) ⬇️
performance-tests 49.50% <ø> (-0.02%) ⬇️
unit-tests 79.59% <ø> (-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:flaky-test-fix PR fixes a flaky test
Projects
Status: Reviewed
Development

Successfully merging this pull request may close these issues.

3 participants