You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we go to third_party/move/tools/move-unit-test and run: MVC_V2=1 MVC_BLOCK_V1=1 cargo test, we see that it panics with "V1 compiler not expected".
But the scripts/move_pr.sh runs these tests with MVC_V2=1 (i.e., the equivalent MOVE_COMPILER_V2=true); we also have baseline files *.v2_exp added with the expectation that these outputs are from running compiler v2. However, all of these actually are just running compiler v1, giving us a false sense of testing.
To reproduce
See steps above.
Expected Behavior
We should be running the tests under third_party/move/tools/move-unit-test with compiler v2 when MVC_V2=1.
The text was updated successfully, but these errors were encountered:
🐛 Bug
If we go to
third_party/move/tools/move-unit-test
and run:MVC_V2=1 MVC_BLOCK_V1=1 cargo test
, we see that it panics with "V1 compiler not expected".But the
scripts/move_pr.sh
runs these tests withMVC_V2=1
(i.e., the equivalentMOVE_COMPILER_V2=true
); we also have baseline files*.v2_exp
added with the expectation that these outputs are from running compiler v2. However, all of these actually are just running compiler v1, giving us a false sense of testing.To reproduce
See steps above.
Expected Behavior
We should be running the tests under
third_party/move/tools/move-unit-test
with compiler v2 whenMVC_V2=1
.The text was updated successfully, but these errors were encountered: