Skip to content

chore: deflake //rs/ledger_suite/icp/ledger:ledger_canister_test#10397

Open
mraszyk wants to merge 1 commit into
masterfrom
mraszyk/deflake-ledger-canister-test
Open

chore: deflake //rs/ledger_suite/icp/ledger:ledger_canister_test#10397
mraszyk wants to merge 1 commit into
masterfrom
mraszyk/deflake-ledger-canister-test

Conversation

@mraszyk
Copy link
Copy Markdown
Contributor

@mraszyk mraszyk commented Jun 5, 2026

This PR deflakes //rs/ledger_suite/icp/ledger:ledger_canister_test: Removed the assertion that archived_ranges.is_empty() after the archive is created. The test still verifies the key property — blocks are never reported in two places simultaneously — but no longer requires catching the ledger in a mid-archiving state. With Rust 1.95.0 (to be bumped in a separate PR), archiving completes within the same ticks used to wait for archive creation.

@github-actions github-actions Bot added the chore label Jun 5, 2026
@mraszyk mraszyk marked this pull request as ready for review June 5, 2026 04:33
@mraszyk mraszyk requested a review from a team as a code owner June 5, 2026 04:33
@github-actions github-actions Bot added the @defi label Jun 5, 2026
@mraszyk mraszyk requested a review from Copilot June 5, 2026 06:11
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR deflakes the state-machine archiving test used by //rs/ledger_suite/icp/ledger:ledger_canister_test by removing a timing-sensitive assertion about archived_ranges being empty immediately after an archive is created, while keeping the core invariant check that a block is never reported in two places at once.

Changes:

  • Removed the assertion that get_blocks_res.archived_ranges.is_empty() right after the archive appears.
  • Updated the surrounding test commentary to focus on the “not reported in two places simultaneously” invariant.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +5123 to +5125
// Verify that block `0` is not reported in two places simultaneously: either it is
// still in local storage (archiving in progress) or it has been moved to the archive
// (archiving completed), but never both at the same time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants