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,4 @@
|
||||
-- empty constr
|
||||
(program 1.1.0
|
||||
(constr 0 )
|
||||
)
|
||||
@@ -0,0 +1,2 @@
|
||||
({cpu: 23100
|
||||
| mem: 200})
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.1.0 (constr 0))
|
||||
@@ -0,0 +1,4 @@
|
||||
-- constr with an argument
|
||||
(program 1.1.0
|
||||
(constr 0 (con integer 1))
|
||||
)
|
||||
@@ -0,0 +1,2 @@
|
||||
({cpu: 46100
|
||||
| mem: 300})
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.1.0 (constr 0 (con integer 1)))
|
||||
@@ -0,0 +1,4 @@
|
||||
-- constr can have arbitrary terms in it
|
||||
(program 1.1.0
|
||||
(constr 1 (con integer 1) (lam x x) (constr 0 (con integer 1)))
|
||||
)
|
||||
@@ -0,0 +1,2 @@
|
||||
({cpu: 115100
|
||||
| mem: 600})
|
||||
@@ -0,0 +1 @@
|
||||
(program 1.1.0 (constr 1 (con integer 1) (lam x x) (constr 0 (con integer 1))))
|
||||
@@ -0,0 +1,4 @@
|
||||
-- constr is strict in all its arguments
|
||||
(program 1.1.0
|
||||
(constr 0 (error))
|
||||
)
|
||||
@@ -0,0 +1 @@
|
||||
evaluation failure
|
||||
@@ -0,0 +1 @@
|
||||
evaluation failure
|
||||
@@ -0,0 +1,4 @@
|
||||
-- constr is strict in all its arguments
|
||||
(program 1.1.0
|
||||
(constr 0 (con integer 1) (error))
|
||||
)
|
||||
@@ -0,0 +1 @@
|
||||
evaluation failure
|
||||
@@ -0,0 +1 @@
|
||||
evaluation failure
|
||||
Reference in New Issue
Block a user