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

tests: sync_after_each_test -> sync_between_tests #9239

Merged
merged 2 commits into from
Oct 2, 2024
Merged

Conversation

jcsp
Copy link
Collaborator

@jcsp jcsp commented Oct 2, 2024

Problem

We are seeing frequent pageserver startup timelines while it calls syncfs(). There is an existing fixture that syncs after tests, but not before the first one. We hypothesize that some failures are happening on the first test in a job.

Summary of changes

  • extend the existing sync_after_each_test to be a sync between all tests, including sync'ing before running the first test. That should remove any ambiguity about whether the sync is happening on the correct node.

This is an alternative to #8957 -- I didn't realize until I saw Alexander's comment on that PR that we have an existing hook that syncs filesystems and can be extended.

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.
  • Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
  • If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

  • Do not forget to reformat commit message to not include the above checklist

@jcsp jcsp added a/test Area: related to testing a/tech_debt Area: related to tech debt run-benchmarks Indicates to the CI that benchmarks should be run for PR marked with this label labels Oct 2, 2024
Copy link

github-actions bot commented Oct 2, 2024

5110 tests run: 4942 passed, 0 failed, 168 skipped (full report)


Flaky tests (1)

Postgres 17

Code coverage* (full report)

  • functions: 31.4% (7489 of 23887 functions)
  • lines: 49.6% (60094 of 121239 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
75899c7 at 2024-10-02T15:38:59.444Z :recycle:

@jcsp jcsp requested review from bayandin and koivunej October 2, 2024 15:46
@jcsp
Copy link
Collaborator Author

jcsp commented Oct 2, 2024

This made it through two benchmark runs without failures, so cautiously optimistic that it at least does no harm

@jcsp jcsp marked this pull request as ready for review October 2, 2024 15:49
Copy link
Member

@bayandin bayandin left a comment

Choose a reason for hiding this comment

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

LGTM, just a minor style-related comment

test_runner/fixtures/compare_fixtures.py Show resolved Hide resolved
Copy link
Member

@koivunej koivunej left a comment

Choose a reason for hiding this comment

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

Let's try this.

Per #8957 (comment) the earlier attempt didn't look promising though. Because we only run single process with I don't see why this would be different, but lets try.

test_runner/fixtures/compare_fixtures.py Show resolved Hide resolved
.github/workflows/build_and_test.yml Show resolved Hide resolved
@jcsp jcsp enabled auto-merge (squash) October 2, 2024 16:13
@jcsp jcsp merged commit d546241 into main Oct 2, 2024
87 checks passed
@jcsp jcsp deleted the jcsp/sync-between-tests branch October 2, 2024 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/tech_debt Area: related to tech debt a/test Area: related to testing run-benchmarks Indicates to the CI that benchmarks should be run for PR marked with this label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants