retesteth does not produce vm trace for some ValidBlock tests

[gurukamath]

I came across a handful of tests within the ValidBlocks folder that do not produce an evm trace with retesteth. I presume this is because these tests have invalid blocks in them. Is there any way of identifying such tests without running them through geth?

Also would it be more appropriate to have those tests in InvalidBlocks?

Example - test for the Berlin hard fork

[winsvega]

in that test trace is not retrived because imported block does not belong to the TOP difficulty chain, therefor thransaction is not found in the latest block.

actually vmtrace in blockchain tests not tested. it is implemented but never tested. see if other cases work.

I think I can fix it to look up for transaction in all known chains and print the vmtrace anyway. but does it make sense if chainreorg does no longer happen after Merge

[winsvega]

added more debug support for blockchain tests
including intermidiate statediffs and vmtrace for a specific transaction

https://ethereum-tests.readthedocs.io/en/latest/retesteth-ref.html#blockchain-test-debugging