dmakarov
commented
1 year ago With corrections in #332 and changes to Solana VM configuration we're down to 7 failures
Test failures:
Failures in 0x1::bcs_tests:
┌── encode_128 ──────
│ Test was not expected to error, but it aborted with code 101 originating in an unknown location rooted here
└──────────────────
Failures in 0x1::vector_tests:
┌── borrow_out_of_range ──────
│ Test did not abort with expected code. Expected test to abort with code 1, but instead it aborted with code 101 originating in an unknown location rooted here
└──────────────────
┌── destroy_non_empty ──────
│ Test did not abort with expected code. Expected test to abort with code 3, but instead it aborted with code 101 originating in an unknown location rooted here
└──────────────────
┌── pop_out_of_range ──────
│ Test did not abort with expected code. Expected test to abort with code 2, but instead it aborted with code 101 originating in an unknown location rooted here
└──────────────────
┌── swap_empty ──────
│ Test did not abort with expected code. Expected test to abort with code 1, but instead it aborted with code 101 originating in an unknown location rooted here
└──────────────────
┌── swap_out_of_range ──────
│ Test did not abort with expected code. Expected test to abort with code 1, but instead it aborted with code 101 originating in an unknown location rooted here
└──────────────────
┌── swap_remove_out_of_range ──────
│ Test did not abort with expected code. Expected test to abort with code 1, but instead it aborted with code 101 originating in an unknown location rooted here
└──────────────────
Test result: FAILED. Total tests: 142; passed: 135; failed: 7
Running Move stdlib unit tests reveals several failures that need to be analyzed (this depends on acceptance of #324)