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
@vgao1996 I had an issue where the CLI silenced the output from the package manager in EVM mode.
For language/tools/move-cli/tests/move_unit_tests/assign_dev_addr_for_dep/Move.toml
If you have B = "0x2"
I would expect my new error from the package manager to show up, instead I get:
test run_all::assign_dev_addr_for_dep/args.evm.txt ... FAILED
Error: Expected output differs from actual output:
Command `package test --evm`:
BUILDING MoveStdlib
BUILDING Bar
BUILDING Foo
Running Move unit tests
[ PASS ] 0x2::M::nop
Test result: OK. Total tests: 1; passed: 1; failed: 0
Error: Unable to resolve packages for package 'Foo'
Caused by:
0: While resolving dependency 'Bar' in package 'Foo'
1: Unable to resolve package dependency 'Bar'
2: While resolving dependency 'MoveStdlib' in package 'Bar'
3: While processing dependency 'MoveStdlib'
4: Unable to find package manifest for 'MoveStdlib' at "Move.toml/./dep/../../../../../../move-stdlib"
The text was updated successfully, but these errors were encountered:
Yeah this is a known bug I'm still investigating. Strangely, the move-unit-test executable seems to be showing the correct error messages, making me suspect the problem is in the move-cli.
@vgao1996 I had an issue where the CLI silenced the output from the package manager in EVM mode.
For
language/tools/move-cli/tests/move_unit_tests/assign_dev_addr_for_dep/Move.toml
If you have
B = "0x2"
I would expect my new error from the package manager to show up, instead I get:
The text was updated successfully, but these errors were encountered: