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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Remove unnecessary work around segmentation faults :)" #1656

Merged
merged 1 commit into from Apr 19, 2023

Conversation

gonzalo-bulnes
Copy link
Contributor

@gonzalo-bulnes gonzalo-bulnes commented Apr 4, 2023

Description

Run the functional tests in isolation (one by one) again, to work around frequent timeouts that don't happen that way.
Details in the commit message! 馃挰

Test Plan

  • CI is green, stays green if you re-build a few times (the occasional segfault is acceptable, but it should be a lot less frequent than we currently observe).

@gonzalo-bulnes gonzalo-bulnes marked this pull request as ready for review April 4, 2023 07:22
@gonzalo-bulnes gonzalo-bulnes requested a review from a team as a code owner April 4, 2023 07:22
@gonzalo-bulnes gonzalo-bulnes added tests 馃崜 Bite-sized This pull request should be very quick to review. 鈿欙笍 Tooling Improving maintainability and increasing maintainer joy : ) labels Apr 4, 2023
It turns out that segmentation faults that I fixed were not the only
cause of flakiness. I haven't found any obvious reason why timeouts
would stop happening when tests run in isolation from each other,
but that seems to work. Remains the occasional segfault, that should
be the exception rather than a regular event.

Restoring the workaround until it becomes worth investigating further.

Trade-off: the functional tests are now 65% longer than the longest job
in the pipeline, which extends the overall time accordingly. The regular
failures did render the time-savings moot, so this actually making
things better, just not as good as they would be without flakiness.

This reverts commit a74c1ef.
@gonzalo-bulnes gonzalo-bulnes force-pushed the restore-functional-tests-flakiness-workaround branch from fb37e1d to 343abff Compare April 4, 2023 07:25
@gonzalo-bulnes
Copy link
Contributor Author

(rebased without changes)

@cfm cfm self-assigned this Apr 10, 2023
Copy link
Member

@cfm cfm left a comment

Choose a reason for hiding this comment

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

Alas! But this looks good after three consecutive runs:

  • CI is green, stays green if you re-build a few times (the occasional segfault is acceptable, but it should be a lot less frequent than we currently observe).

Thanks, @gonzalo-bulnes.

@cfm cfm merged commit 1d0006a into main Apr 19, 2023
18 checks passed
@cfm cfm deleted the restore-functional-tests-flakiness-workaround branch April 19, 2023 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
鈿欙笍 Tooling Improving maintainability and increasing maintainer joy : ) 馃崜 Bite-sized This pull request should be very quick to review. tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants