-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Bug][move-compiler-v2] compiler-v2 fails vm_test_harness/example.move test #13255
Comments
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 previous code as a "to be compiled" source, but if there is a conflict with the later source we have a problem. |
@wrwg @brmataptos, this error happens because when running expansion phase in V2, all modules |
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 to the package builder, but we need to test module upgrade cases as would be done by real users. |
See
in #13216 .
There might be some problem with the test harness, but
task 4
of the test case fails compilation withMOVE_COMPILER_V2=true
.The text was updated successfully, but these errors were encountered: