Complete M7.9b upgrade barrier and durability qualification

Schema v8 binds authority to builds (ADR-0068): acquisition names the
host build and only retained, unretired builds may hold a lease; no
commit may name a retired build; upgrade_barrier retires a build and
fences every holder in one transaction, while build-less pre-v8 hosts
keep working until the first barrier. Tests cover a writer surviving a
failed and then a real online migration, old-writer fencing on every
path, whole-history recovery by the new build, and the M7 qualification
fixture (19.6 s SIGKILL-to-ready under the production lease, no lost
acknowledgements).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-29 07:31:04 -04:00
co-authored by Claude Opus 5.5
parent 703f67834f
commit f59cca2c3b
24 changed files with 893 additions and 52 deletions
+3
View File
@@ -10,6 +10,7 @@ void run_region_server_process_tests();
void run_region_recovery_tests();
void run_region_ops_tests();
void run_region_clone_tests();
void run_region_migration_tests();
namespace {
using namespace evo::persistence;
using namespace std::chrono_literals;
@@ -90,6 +91,8 @@ int main() {
std::puts("region ops integration passed");
run_region_clone_tests();
std::puts("region clone and history integration passed");
run_region_migration_tests();
std::puts("region migration, barrier and qualification integration passed");
return 0;
} catch (const std::exception& e) {
std::fprintf(stderr, "%s\n", e.what());