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

improve comments in identify_levels #7777

Draft
wants to merge 1 commit into
base: problame/tiered-compaction/identify-levels-bails-too-early
Choose a base branch
from

Conversation

hlinnaka
Copy link
Contributor

Follow up to PR #7775

@@ -310,22 +349,45 @@ mod tests {
}

#[tokio::test]
async fn repro_identify_levels_bails_too_ealy_if_partitioned_keyspace_same_lsn() -> anyhow::Result<()> {
async fn test_disjoint_key_ranges_same_lsn() -> anyhow::Result<()> {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure this test case still makes sense, given that the original problem it was written to demonstrate turned out to be a red herring. identify_levels() doesn't pay any attention to the key ranges, so testing with partitioned keyspace isn't that different from the existing tests.

Copy link

3060 tests run: 2933 passed, 0 failed, 127 skipped (full report)


Flaky tests (1)

Postgres 16

  • test_statvfs_pressure_usage: release

Code coverage* (full report)

  • functions: 31.5% (6352 of 20180 functions)
  • lines: 47.5% (48032 of 101088 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
272416a at 2024-05-16T10:14:25.316Z :recycle:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant