Scotty

> Numbers of overall tests do not yet get together though completely, so e.g. same blockchain tests/same fork atm have different numbers of overall run tests, guess that's something which...

`npx vitest test/tester/blockchain/stEIP5656-MCOPY` will run the MCOPY tests in the blockchain runner

This is the `coverage` report for the MCOPY tests:  Does he really mean that this should be 100% if the tests all run??

The remaining failures in the CI are heap memory errors in the larger blockchain tests. i imagine there's a way around that?

> Hi there, what’s the status of this? :-) > > (I the hell can’t find the emojis on my iPad keyboard #insert laughing emoji here#) @holgerd77 I feel confident...

On another review, I am second guess myself regarding this "speedy" test run actually running all of the code :unamused: However a "slow" run is very very slow. (up to...

It almost feels like it runs through the whole thing twice. Once to count the number of tests and set up the reporting. And then again to run the tests?...

This is what slow but honest test results look like:  ~ 4 minutes

> Also, I think we need to study how to multithread vitest and how this works. There are a lot of suite (this seems to be the same as describe?)...

@TimDaub -- The "optimizations" you mentioned kind of obscure my ability to conceive of the Ethereum Trie in "Levels" like an ordinary merkle tree. The "Patricia" structure is condensed prior...