Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reactivate page bench test in CI after ignoring CopyFail error in pag…
…eserver (#8023) ## Problem Testcase page bench test_pageserver_max_throughput_getpage_at_latest_lsn had been deactivated because it was flaky. We now ignore copy fail error messages like in https://github.com/neondatabase/neon/blob/270d3be507643f068120b52838c497f6c1b45b61/test_runner/regress/test_pageserver_getpage_throttle.py#L17-L20 and want to reactivate it to see it it is still flaky ## Summary of changes - reactivate the test in CI - ignore CopyFail error message during page bench test cases ## 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
- Loading branch information
9ba9f32
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3298 tests run: 3146 passed, 1 failed, 151 skipped (full report)
Failures on Postgres 14
test_pageserver_max_throughput_getpage_at_latest_lsn[github-actions-selfhosted-10-6-30]
: releaseFlaky tests (1)
Postgres 14
test_storage_controller_smoke
: releaseCode coverage* (full report)
functions
:31.6% (6633 of 20989 functions)
lines
:48.6% (51498 of 106042 lines)
* collected from Rust tests only
9ba9f32 at 2024-06-12T15:34:25.780Z :recycle: