-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VM: State/Blockchain Test Runs with Bun fail #3223
Comments
I can take a look at this by tomorrow afternoon the latest? 😃👍 |
@jochem-brouwer Sounds good, that would be nice! 👍 |
First note here: the error messages point to the esm build output, not to the original |
Test results by using In await this.journal.putAccount(message.to, toAccount)
;(<any>Address).abcde = 123
console.log((<any>Address).abcde)
await this.stateManager.clearContractStorage(message.to)
const newContractEvent = {
address: message.to,
code: message.code,
} This adds this In /**
* Clears all storage entries for the account corresponding to `address`.
* @param address - Address to clear the storage of
*/
async clearContractStorage(address: Address): Promise<void> {
console.log((<any>Address).abcde) This will print:
So it looks like somehow Bun is importing the same constructors from two different files 🤔 Not sure how to proceed here though. Note: if this is tested using |
It seems that VM and EVM run on CJS (so also their imports), but StateManager (as imported in the general state tests runner), runs on ESM 🤔 |
Short update: tested this with bun |
Running the VM state/blockchain tests with
Bun
currently fails (see #3219 for additional context). The error message is pretty generic, so it is likely generally worth looking into this."Pure" test run with
tsx
can be done with:(from the VM package folder)
Running with
Bun
can be triggered with:This gives the following breakage after a couple of successful test proceedings:
So: pretty basic error (ignore the red whiggle underlinings, just some formatting).
As mentioned above, likely worth to give this a look, maybe this gives some additional insights.
The text was updated successfully, but these errors were encountered: