Open shamb0 opened 1 year ago
Copying @raulk comments here
It's the opposite. This was happening because the test code previously used the "create account" method on the EAM and the EAM refused to deploy code to some of our reserved addresses.
As far as I can tell, these tests now work.
Er, well, no. The first one is passing. The second one is failing with:
02: f01107 (method 2) -- can only resurrect a dead contract (18)
Ok, so, yeah. Everything but ID-0056 passes.
@Stebalien, tested with your Patch. All the use-cases looks fine for me under WASM context. Added Trace file for reference.
Issue can be closed after acceptance review.
ID | Use-Case | Status | Trace |
---|---|---|---|
TID-04-121 | stBadOpcode/undefinedOpcodeFirstByte | OK | Trace |
TID-13-34 | stCreate2/Create2OOGFromCallRefunds | OK | Trace |
TID-14-37 | stCreateTest/CreateOOGFromCallRefunds | OK | Trace |
TID-23-21 | stExtCodeHash/extCodeHashDynamicArgument | OK | Trace |
TID-31-098 | stPreCompiledContracts2/modexp_0_0_0_20500 | OK | Trace |
TID-31-099 | stPreCompiledContracts2/modexp_0_0_0_22000 | OK | Trace |
TID-31-100 | stPreCompiledContracts2/modexp_0_0_0_25000 | OK | Trace |
TID-31-101 | stPreCompiledContracts2/modexp_0_0_0_35000 | OK | Trace |
In:
stCreate2/Create2OOGFromCallRefunds
I'm seeing a lot of failures. Are those expected?
Hit with error "failed to create the new actor :: cannot create address with a reserved prefix".
Have to check validity of eth address in the below test suites.