test_location_conf_churn fails with "could not read block" error on attempt to download deleted layer

TL;DR: [alexanderlaw (reporter)]: @jcsp , thank you for the fix! (I run this test on my Linux laptop, and I guess the failure could be timing-dependent, so may be for reproducing it, the test duration should be approximately the same as shown above.) Yeah, I'll start testing it now (I'd test it for several hours to be sure). Context: GitHub issue neondatabase/neon#11348 (closed, 28 comments): Several failures of the testlocationconfchurn test: YOURHOST.s3.amazonaws.com/reports/pr-10537/13725294150/index.html#testresult/9985f1fcf2c1267a testlocationconfchurn[debug-pg17-2] / X64 / lfc: 'without-lfc' / seed: 2 YOURHOST.s3.amazonaws.com/reports/pr-10841/13440141402/index.html#testresult/3f38c46eb2f7cc testlocationconfchurn[release-pg17-2] / ARM64 / _lfc: 'without-lfc' / seed: 2 with the following diagnostics:

test_location_conf_churn fails with "could not read block" error on attempt to download deleted layer

Fix

1. [alexanderlaw (reporter)]: @jcsp , thank you for the fix! (I run this test on my Linux laptop, and I guess the failure could be timing-dependent, so may be for reproducing it, the test duration should be approximately the same as shown above.) Yeah, I'll start testing it now (I'd test it for several hours to be sure). Expected: this specific failure stops.

Details

Context: GitHub issue neondatabase/neon#11348 (closed, 28 comments): Several failures of the testlocationconfchurn test: YOURHOST.s3.amazonaws.com/reports/pr-10537/13725294150/index.html#testresult/9985f1fcf2c1267a testlocationconfchurn[debug-pg17-2] / X64 / lfc: 'without-lfc' / seed: 2 YOURHOST.s3.amazonaws.com/reports/pr-10841/13440141402/index.html#testresult/3f38c46eb2f7cc testlocationconfchurn[release-pg17-2] / ARM64 / lfc: 'without-lfc' / seed: 2 with the following diagnostics: ` testrunner/regress/testpageserversecondary.py:245: in testlocationconfchurn workload.churnrows( test_runner/fixt

When to use

You hit exactly this: testlocationconfchurn fails with "could not read block" error on attempt to download deleted layer in testlocationconfchurn.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

testlocationconf_churn.

GitHub issue neondatabase/neon#11348 (closed, 28 comments): Several failures of the testlocationconfchurn test: https://neon-github-public-dev.s3.amazonaws.com/reports/pr-10537/13725294150/index.html#testresult/9985f1fcf2c1267a testlocationconfchurn[debug-pg17-2] / X64 / _lfc: 'without-lfc' / seed: 2 https://neon-github-public-dev.s3.amazonaws.com/reports/pr-10841/13440141402/index.html#testresult/3f38c46eb2f7cc testlocationconfchurn[release-pg17-2] / ARM64 / _lfc: 'without-lfc' / seed: 2 with the following diagnostics: ``` testrunner/regress/testpageserversecondary.py:245: in testlocationconfchurn workload.churnrows( test_runner/fixt Verified answer: [alexanderlaw (reporter)]: @jcsp , thank you for the fix! (I run this test on my Linux laptop, and I guess the failure could be timing-dependent, so may be for reproducing it, the test duration should be approximately the same as shown above.) Yeah, I'll start testing it now (I'd test it for several hours to be sure). Source: https://github.com/neondatabase/neon/issues/11348