Add PlutusV3 conformance tests and also control budgets
There were some odd discrepancy for `integerToByteString` on the mem side. Either 1 or about 1000 mem units off; which I couldn't quite figure out. Yet, it proves useful to validate builtin at large and ensure we have a valid cost model for v3.
This commit is contained in:
@@ -0,0 +1,3 @@
|
||||
(program 1.0.0
|
||||
[(lam x (con integer 4)) (delay (error))]
|
||||
)
|
||||
@@ -0,0 +1,2 @@
|
||||
({cpu: 92100
|
||||
| mem: 500})
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.0.0 (con integer 4))
|
||||
@@ -0,0 +1,3 @@
|
||||
(program 1.0.0
|
||||
[(lam x x) (delay (error))]
|
||||
)
|
||||
@@ -0,0 +1,2 @@
|
||||
({cpu: 92100
|
||||
| mem: 500})
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.0.0 (delay (error )))
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.0.0 (lam x (delay x)))
|
||||
@@ -0,0 +1,2 @@
|
||||
({cpu: 23100
|
||||
| mem: 200})
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.0.0 (lam x (delay x)))
|
||||
Reference in New Issue
Block a user