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,51 @@
(program
1.0.0
[
[
[
(force
(delay
(lam
f
[
(force
(force
(delay
(delay
(lam
f
[
(force (delay (lam s [ s s ])))
(lam
s
(lam
x
[
[ f [ (force (delay (lam s [ s s ]))) s ] ] x
]
)
)
]
)
)
)
)
)
(lam
rec
(lam
z
(lam n [ [ (force n) z ] (lam n' [ [ rec [ f z ] ] n' ]) ])
)
)
]
)
)
)
[ (builtin addInteger) (con integer 1) ]
]
(con integer 0)
]
[ (lam n (delay (lam z (lam f [ f n ])))) (delay (lam z (lam f z))) ]
]
)

View File

@@ -0,0 +1,2 @@
({cpu: 2207577
| mem: 8802})

View File

@@ -0,0 +1 @@
(program 1.0.0 (con integer 1))