Split a couple of tests in two to avoid CPU limit#3402
Merged
Conversation
mkoura
approved these changes
Apr 15, 2026
Contributor
Author
|
@mkoura Do these tests work OK now? I tried running them on my own machine and still got a failure, but I may have done something wrong. |
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.
The
succeedingG2MultiScalarMulPolicyScript1_V3_110succeedingG2MultiScalarMulPolicyScript2_V3_110end-to-end tests for Plutus were failing because the scripts were exceeding the on-chain CPU limit (10,000,000,000 units). To avoid this I've split each script into anaand abversion which each do about half of the computation that the original scripts do. Executing these scripts directly using the Plutus Core interpreter shows that they all complete successfully without exceeding the limit, but I still get errors when running the node tests locally.I'm not sure what the problem is. It may be that I need to replace the
UNKNOWN_PER_TIMEandUNKNOWN_PER_SPACEvalues with something sensible, but I'm not sure what that should be.