Brian R. Murphy

> * I'm not seeing what this PR brings us in new quality of testing since most features we have v2 tests for now are rather generic Move code which...

> Hi @brmataptos, sorry I don't look all code and new files in detail because there are so many. I am wondering how these tests are run against the compiler...

We have several situations where V2 can generate a lot of warnings on a line. We should do this for V2. maybe attributes.

This is related to #13392. Namely, the problem is that the transactional tests just simulate publishing code, but don't really publish it anywhere. This means we have to treat the...

We need to test this case when building a new module when there is an existing module of the same name and address on-chain already. Maybe this just works due...

I've managed to see this problem intermittently but can't reproduce it reliably. I think that (1) the libraries are being built without `#[test_only]` code, but then a user `#[test]` function...

This has been hard to reproduce, but I found it happening in a case where I had files from a previous build/tool left behind in a Move package build/ directory,...

I'm not sure if this appears in `aptos move disassemble` but if we try to run move-cli tests with `MOVE_COMPILER_V2=true` we hit this failure. So it's likely we'll see the...

@wrwg Do you recall where/how you saw this bug?

I'm not sure if the problem I just found and fixed is the one which Wolfgang mentioned originally, as I see an error with disassembly which occurs either with the...