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:
KtorZ
2024-08-14 02:42:04 +02:00
parent f879f6d183
commit 2cb87f4f8f
2893 changed files with 6385 additions and 13 deletions

View File

@@ -0,0 +1,4 @@
-- empty constr
(program 1.1.0
(constr 0 )
)

View File

@@ -0,0 +1,2 @@
({cpu: 23100
| mem: 200})

View File

@@ -0,0 +1 @@
(program 1.1.0 (constr 0))

View File

@@ -0,0 +1,4 @@
-- constr with an argument
(program 1.1.0
(constr 0 (con integer 1))
)

View File

@@ -0,0 +1,2 @@
({cpu: 46100
| mem: 300})

View File

@@ -0,0 +1 @@
(program 1.1.0 (constr 0 (con integer 1)))

View File

@@ -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)))
)

View File

@@ -0,0 +1,2 @@
({cpu: 115100
| mem: 600})

View File

@@ -0,0 +1 @@
(program 1.1.0 (constr 1 (con integer 1) (lam x x) (constr 0 (con integer 1))))

View File

@@ -0,0 +1,4 @@
-- constr is strict in all its arguments
(program 1.1.0
(constr 0 (error))
)

View File

@@ -0,0 +1 @@
evaluation failure

View File

@@ -0,0 +1 @@
evaluation failure

View File

@@ -0,0 +1,4 @@
-- constr is strict in all its arguments
(program 1.1.0
(constr 0 (con integer 1) (error))
)

View File

@@ -0,0 +1 @@
evaluation failure

View File

@@ -0,0 +1 @@
evaluation failure