🌱 Add constant seeds for integration tests and demo CLI #26
Conversation
This file contains 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
ZamDimon
changed the title
ZamDimon
previously approved these changes
Oct 28, 2024
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.
🔍 Objective
As before the behavior of integration tests for "disprove" spending checks was random, the CI sometimes didn't pass as the algorithm may create too large blocks or the script caused the "Stack limit exceeds" error, which wasn't a problem as integration tests only checked the "spending" behavior and bugs will be fixed later.
🆕 Added
Constant seeds for integration tests and demo CLI for distorted states.
✅ Checklist
READMEfiles, paper) and Code Comments are updated accordingly.