Fix spurious test failures due to accidental zero token transfers#2083
Merged
ImplOfAnImpl merged 1 commit intoJun 19, 2026
Merged
Conversation
OBorce
approved these changes
Jun 18, 2026
ImplOfAnImpl
deleted the
fix_spurious_test_failures_due_to_zero_token_transfers
branch
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
2 participants
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.
Tests by default use the latest chainstate upgrades, where zero token transfers are no longer allowed. And currently some tests may accidentally create zero token outputs and fail because of this.
Here I fix an actual failure that I got on CI plus all other places that I could find that can potentially produce a zero token output.