test: retarget isolated Axis B fixture to v2.6.0 #103
Loading…
Reference in a new issue
No description provided.
Delete branch "test/v260-axis-b-fixture"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The deterministic Axis B fixture still pinned official v2.5.1 client/Go ingress and used an ambiguous
IVNP_AXIS_B_PASStoken for a network-isolated artifact-equivalence run. Neither is valid evidence for public deployed v2.6.0.Change
695b60121b9aba68c4612a9bb990e086a2bfd36fand official ARM64 clients; verify published.sha256and hardcoded downloaded-byte hashes.public_deployed_path_verified=false, not a public release pass.Validation
bash -n scripts/v240-axis-b-ivnp-smoke.sh; static fixture contract tests in normal andPYTHONOPTIMIZE=1environmentscargo test --locked(198 passed, 3 ignored), fmt/check/clippy, Go IVNP helper testsThis PR must pass both required CI contexts on its exact head before merge. It does not remove the release worker's public gate latch.