e2e: expand and parallelize backward compatibility test#2869
Open
e2e: expand and parallelize backward compatibility test#2869
Conversation
…y test - Add user lifecycle: accesspass_set, user_create, user_wait_activated, user_update, user_delete, accesspass_close - Add user ban workflow with request-ban and delete - Add multicast subscription and allowlist operations - Add DZX link lifecycle: create, accept, update, delete - Add exchange_clear_devices step before device deletion - Add device_wait_removed steps to ensure proper cleanup order - Add get commands for all entity types - Add health commands for devices and links
- Add set-health commands to knownIncompatibilities (added in v0.8.6) - Fix diagnostic output to use fmt.Println to preserve newlines
d27c708 to
66e382b
Compare
Run CLI version subtests in parallel against a shared devnet stack instead of sequentially. Each version already creates entities with version-specific codes and IPs, so they don't conflict. Three shared-state steps (cloned entity updates, global config set) are made version-specific to avoid Solana write-lock conflicts. CLI version installation is batched into a single docker exec call to eliminate repeated roundtrips and apt reinstalls.
| // --- Phase 15: Delete operations --- | ||
| // Test delete instructions in reverse dependency order. | ||
| // The onchain program enforces referential integrity: | ||
| // - Users must be deleted before accesspasses can be closed |
Contributor
There was a problem hiding this comment.
Is Greg's PR in? I think there is a change that will fix the deadlock situation we reached with multicast groups subs and user deletion
martinsander00
approved these changes
Feb 8, 2026
Fix WAN vs DZX link description: WAN links connect devices owned by the same contributor, DZX links are cross-contributor peering links. Remove outdated note about banned multicast user deletion issue, which was fixed in #2830.
This reverts commit 2de13b1.
Add known incompatibilities for: - Multicast operations (< 0.8.1): depend on multicast_group_create which fails due to Borsh struct change, so all dependent ops fail with "MulticastGroup not found" - global_config_set (< 0.8.7): SetGlobalConfig unconditionally requires resource extension accounts added in #2650 and #2849, even for the update path where they aren't used
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
Testing Verification