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: make Workload more determinstic #10741

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

tests: make Workload more determinstic #10741

wants to merge 3 commits into from

Conversation

jcsp
Copy link
Collaborator

@jcsp jcsp commented Feb 10, 2025

Problem

Previously, Workload was reconfiguring the compute before each run of writes, which was meant to be a no-op when nothing changed, but was actually writing extra data due to an issue being fixed in #10696.

The row counts in tests were too low in some cases, these tests were only working because of those extra writes that shouldn't have been happening, and moreover were relying on checkpoints happening.

Summary of changes

  • Only reconfigure compute if the attached pageserver actually changed. If pageserver is set to None, that means controller is managing everything, so never reconfigure compute.
  • Update tests that wrote too few rows.

Copy link

7425 tests run: 6944 passed, 122 failed, 359 skipped (full report)


Failures on Postgres 17

Failures on Postgres 16

Failures on Postgres 15

Failures on Postgres 14

# Run all failed tests locally:
scripts/pytest -vv -n $(nproc) -k "test_location_conf_churn[release-pg14-3] or test_location_conf_churn[release-pg14-3] or test_location_conf_churn[release-pg14-2] or test_location_conf_churn[release-pg14-2] or test_location_conf_churn[release-pg14-1] or test_location_conf_churn[release-pg14-1] or test_sharding_smoke[release-pg14] or test_sharding_smoke[release-pg14] or test_sharding_backpressure[release-pg14] or test_sharding_backpressure[release-pg14] or test_sharding_split_failures[release-pg14-failure5] or test_sharding_split_failures[release-pg14-failure2] or test_sharding_split_failures[release-pg14-failure2] or test_sharding_split_failures[release-pg14-failure6] or test_sharding_split_failures[release-pg14-failure11] or test_sharding_split_failures[release-pg14-failure11] or test_sharding_split_failures[release-pg14-failure13] or test_sharding_split_failures[release-pg14-failure15] or test_sharding_split_failures[release-pg14-failure15] or test_sharding_split_failures[release-pg14-failure9] or test_sharding_split_failures[release-pg14-failure16] or test_sharding_split_failures[release-pg14-failure16] or test_sharding_split_failures[release-pg14-failure17] or test_scrubber_physical_gc_ancestors[release-pg14-2] or test_location_conf_churn[release-pg15-3] or test_location_conf_churn[release-pg15-3] or test_location_conf_churn[release-pg15-1] or test_location_conf_churn[release-pg15-1] or test_location_conf_churn[release-pg15-2] or test_sharding_smoke[release-pg15] or test_sharding_smoke[release-pg15] or test_sharding_split_failures[release-pg15-failure5] or test_sharding_split_failures[release-pg15-failure4] or test_sharding_split_failures[release-pg15-failure4] or test_sharding_split_failures[release-pg15-failure6] or test_sharding_split_failures[release-pg15-failure6] or test_sharding_split_failures[release-pg15-failure7] or test_sharding_split_failures[release-pg15-failure10] or test_sharding_split_failures[release-pg15-failure17] or test_sharding_split_failures[release-pg15-failure15] or test_sharding_split_failures[release-pg15-failure15] or test_sharding_split_failures[release-pg15-failure2] or test_sharding_split_failures[release-pg15-failure2] or test_sharding_backpressure[release-pg15] or test_sharding_backpressure[release-pg15] or test_sharding_split_failures[release-pg15-failure8] or test_sharding_split_failures[release-pg15-failure8] or test_sharding_split_failures[release-pg15-failure11] or test_sharding_split_failures[release-pg15-failure11] or test_sharding_split_failures[release-pg15-failure16] or test_sharding_split_failures[release-pg15-failure16] or test_scrubber_physical_gc_ancestors[release-pg15-2] or test_location_conf_churn[release-pg16-3] or test_location_conf_churn[release-pg16-3] or test_location_conf_churn[release-pg16-2] or test_location_conf_churn[release-pg16-2] or test_location_conf_churn[release-pg16-1] or test_location_conf_churn[release-pg16-1] or test_sharding_smoke[release-pg16] or test_sharding_smoke[release-pg16] or test_sharding_backpressure[release-pg16] or test_sharding_backpressure[release-pg16] or test_sharding_split_failures[release-pg16-failure6] or test_sharding_split_failures[release-pg16-failure6] or test_sharding_split_failures[release-pg16-failure2] or test_sharding_split_failures[release-pg16-failure2] or test_sharding_split_failures[release-pg16-failure10] or test_sharding_split_failures[release-pg16-failure9] or test_sharding_split_failures[release-pg16-failure17] or test_sharding_split_failures[release-pg16-failure11] or test_sharding_split_failures[release-pg16-failure11] or test_sharding_split_failures[release-pg16-failure15] or test_sharding_split_failures[release-pg16-failure15] or test_sharding_split_failures[release-pg16-failure16] or test_sharding_split_failures[release-pg16-failure16] or test_scrubber_physical_gc_ancestors[release-pg16-2] or test_location_conf_churn[release-pg17-3] or test_location_conf_churn[release-pg17-3] or test_location_conf_churn[release-pg17-3] or test_location_conf_churn[release-pg17-3] or test_location_conf_churn[debug-pg17-3] or test_location_conf_churn[release-pg17-1] or test_location_conf_churn[release-pg17-1] or test_location_conf_churn[debug-pg17-1] or test_location_conf_churn[release-pg17-1] or test_location_conf_churn[release-pg17-1] or test_location_conf_churn[release-pg17-2] or test_location_conf_churn[debug-pg17-2] or test_location_conf_churn[release-pg17-2] or test_sharding_backpressure[release-pg17] or test_sharding_backpressure[release-pg17] or test_sharding_backpressure[release-pg17] or test_sharding_backpressure[debug-pg17] or test_sharding_backpressure[release-pg17] or test_sharding_split_failures[release-pg17-failure7] or test_sharding_split_failures[release-pg17-failure2] or test_sharding_split_failures[release-pg17-failure2] or test_sharding_split_failures[debug-pg17-failure2] or test_sharding_split_failures[release-pg17-failure2] or test_sharding_split_failures[release-pg17-failure2] or test_sharding_split_failures[release-pg17-failure15] or test_sharding_split_failures[release-pg17-failure15] or test_sharding_split_failures[debug-pg17-failure15] or test_sharding_split_failures[release-pg17-failure15] or test_sharding_split_failures[release-pg17-failure15] or test_sharding_split_failures[release-pg17-failure11] or test_sharding_split_failures[release-pg17-failure11] or test_sharding_split_failures[release-pg17-failure11] or test_sharding_split_failures[release-pg17-failure16] or test_sharding_split_failures[release-pg17-failure16] or test_sharding_split_failures[release-pg17-failure16] or test_sharding_split_failures[debug-pg17-failure16] or test_sharding_split_failures[release-pg17-failure16] or test_sharding_split_failures[release-pg17-failure13] or test_sharding_split_failures[release-pg17-failure17] or test_sharding_split_failures[release-pg17-failure17] or test_sharding_split_failures[release-pg17-failure17] or test_sharding_split_failures[release-pg17-failure8] or test_sharding_split_failures[release-pg17-failure9] or test_sharding_split_failures[release-pg17-failure9] or test_scrubber_physical_gc_ancestors[release-pg17-2] or test_scrubber_physical_gc_ancestors[debug-pg17-2]"
Flaky tests (44)

Postgres 17

Postgres 16

Postgres 15

Postgres 14

Test coverage report is not available

The comment gets automatically updated with the latest test results
5e6bf2d at 2025-02-10T13:36:44.979Z :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.

1 participant