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

Fix flakiness for gui unit_tests #7077

Merged
merged 3 commits into from
Feb 2, 2024

Conversation

jonathan-eq
Copy link
Contributor

@jonathan-eq jonathan-eq commented Feb 1, 2024

Resolves #7071
Resolves #7042
Resolves #7070

Improves flakiness of unit_tests/gui/test_main_window::test_that_run_dialog_can_be_closed_after_used_to_open_plots by increasing timeout time for done_button to be enabled. In a different fixture, the timeout for running the experiment is set to 200.000, while here it was only 20.000. This commit increases this timeout to 200.000.

When running some of the gui unit tests in parallell, they would share storage. This was very prevalent for the test unit_tests/gui/test_main_window.py::test_that_gui_plotter_works_when_no_data, where the PlotApi would return data from the other tests (which running esmda). This is fixed in this PR by mocking the return value from PlotApi.

  • 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 tests pass locally (after every commit!)

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

Improves flakiness of unit_tests/gui/test_main_window::test_that_run_dialog_can_be_closed_after_used_to_open_plots by increasing timeout time for done_button to be enabled. This also applies to unit_tests/gui/simulation/test_run_dialog.py::test_that_run_dialog_can_be_closed_while_file_plot_is_open. In a different fixture, the timeout for running the experiment is set to 200.000, while here it was only 20.000. This commit increases this timeout to 200.000.
@jonathan-eq jonathan-eq marked this pull request as ready for review February 2, 2024 06:35
@jonathan-eq jonathan-eq self-assigned this Feb 2, 2024
@jonathan-eq jonathan-eq added bug flaky-test release-notes:skip If there should be no mention of this in release notes and removed bug labels Feb 2, 2024
@jonathan-eq jonathan-eq changed the title Fix flakiness gui/test_main_window unittest Fix flakiness for gui unit_tests Feb 2, 2024
@jonathan-eq jonathan-eq enabled auto-merge (squash) February 2, 2024 08:58
@jonathan-eq jonathan-eq disabled auto-merge February 2, 2024 09:38
When running some of the gui unit tests in parallell, they would share storage. This was very prevalent for the test unit_tests/gui/test_main_window.py::test_that_gui_plotter_works_when_no_data, where the PlotApi would return data from the other tests (which running esmda). This is fixed in this commit by mocking the return value from PlotApi.
Increase timeout to 60s for integration_tests/scheduler/test_integration_local_driver.py::test_subprocesses_live_on_after_ert_dies.
@jonathan-eq jonathan-eq enabled auto-merge (squash) February 2, 2024 10:45
@jonathan-eq jonathan-eq merged commit 848c2be into equinor:main Feb 2, 2024
51 checks passed
@jonathan-eq jonathan-eq deleted the fix-flaky-gui-test branch February 2, 2024 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test release-notes:skip If there should be no mention of this in release notes
Projects
Archived in project
2 participants