[TEST] How to get Test Error Logs?

[ghost]

The test information within

https://developers.eos.io/eosio-nodeos/docs/build-validation

is quite limited. How can someone:

1. Get information about problems (test error log) ?
2. Run only one test?

I build on a Win10 Pro WSL (ubuntu 16.04), but some tests fail/hang, so i would need more granulated tests and test debug output:

:~/eos/build$ make test
Running tests...
Test project /home/lazaridiscom/eos/build
      Start  1: test_cypher_suites
 1/41 Test  #1: test_cypher_suites ...................   Passed    0.11 sec
      Start  2: validate_simple.token_abi
 2/41 Test  #2: validate_simple.token_abi ............   Passed    0.43 sec
      Start  3: validate_eosio.token_abi
 3/41 Test  #3: validate_eosio.token_abi .............   Passed    0.07 sec
      Start  4: validate_eosio.msig_abi
 4/41 Test  #4: validate_eosio.msig_abi ..............   Passed    0.06 sec
      Start  5: validate_eosio.sudo_abi
 5/41 Test  #5: validate_eosio.sudo_abi ..............   Passed    0.08 sec
      Start  6: validate_multi_index_test_abi
 6/41 Test  #6: validate_multi_index_test_abi ........   Passed    0.07 sec
      Start  7: validate_eosio.system_abi
 7/41 Test  #7: validate_eosio.system_abi ............   Passed    0.08 sec
      Start  8: validate_identity_abi
 8/41 Test  #8: validate_identity_abi ................   Passed    0.07 sec
      Start  9: validate_identity_test_abi
 9/41 Test  #9: validate_identity_test_abi ...........   Passed    0.08 sec
      Start 10: validate_stltest_abi
10/41 Test #10: validate_stltest_abi .................   Passed    0.07 sec
      Start 11: validate_exchange_abi
11/41 Test #11: validate_exchange_abi ................   Passed    0.07 sec
      Start 12: validate_test.inline_abi
12/41 Test #12: validate_test.inline_abi .............   Passed    0.07 sec
      Start 13: validate_hello_abi
13/41 Test #13: validate_hello_abi ...................   Passed    0.06 sec
      Start 14: validate_asserter_abi
14/41 Test #14: validate_asserter_abi ................   Passed    0.08 sec
      Start 15: validate_infinite_abi
15/41 Test #15: validate_infinite_abi ................   Passed    0.06 sec
      Start 16: validate_proxy_abi
16/41 Test #16: validate_proxy_abi ...................   Passed    0.07 sec
      Start 17: validate_test_api_abi
17/41 Test #17: validate_test_api_abi ................   Passed    0.06 sec
      Start 18: validate_test_api_mem_abi
18/41 Test #18: validate_test_api_mem_abi ............   Passed    0.06 sec
      Start 19: validate_test_api_db_abi
19/41 Test #19: validate_test_api_db_abi .............   Passed    0.07 sec
      Start 20: validate_test_api_multi_index_abi
20/41 Test #20: validate_test_api_multi_index_abi ....   Passed    0.07 sec
      Start 21: validate_test_ram_limit_abi
21/41 Test #21: validate_test_ram_limit_abi ..........   Passed    0.09 sec
      Start 22: validate_eosio.bios_abi
22/41 Test #22: validate_eosio.bios_abi ..............   Passed    0.07 sec
      Start 23: validate_noop_abi
23/41 Test #23: validate_noop_abi ....................   Passed    0.06 sec
      Start 24: validate_dice_abi
24/41 Test #24: validate_dice_abi ....................   Passed    0.08 sec
      Start 25: validate_tic_tac_toe_abi
25/41 Test #25: validate_tic_tac_toe_abi .............   Passed    0.08 sec
      Start 26: validate_payloadless_abi
26/41 Test #26: validate_payloadless_abi .............   Passed    0.09 sec
      Start 27: unit_test_binaryen
27/41 Test #27: unit_test_binaryen ...................   Passed  410.77 sec
      Start 28: unit_test_wavm
28/41 Test #28: unit_test_wavm .......................   Passed  944.30 sec
      Start 29: validate_deferred_test_abi
29/41 Test #29: validate_deferred_test_abi ...........   Passed    0.16 sec
      Start 30: plugin_test
30/41 Test #30: plugin_test ..........................   Passed    0.62 sec
      Start 31: nodeos_sanity_test
31/41 Test #31: nodeos_sanity_test ...................***Failed    4.00 sec
      Start 32: nodeos_run_test
32/41 Test #32: nodeos_run_test ......................***Failed    0.57 sec
      Start 33: p2p_dawn515_test
33/41 Test #33: p2p_dawn515_test .....................   Passed   12.87 sec
      Start 34: nodeos_run_test-mongodb
34/41 Test #34: nodeos_run_test-mongodb ..............***Failed  127.93 sec
      Start 35: distributed-transactions-test

[heifner]

WSL is untested and no surprise that you have issues. Last I checked the shared memory support on WSL has issues. You can run with ctest --output-on-failure to see failure output. You can look at ctest --help for other options including how to run individual tests.

[jgiszczak]

In the build directory, you can run ctest --output-on-failure -R <regex> with a regular expression matching the test(s) you want to run. The full name of a specific test counts as a regular expression.

$ ctest --output-on-failure -R nodeos_sanity_test
Test project /home/giszczakj/Dev/eos/build/relwithdebinfo
    Start 32: nodeos_sanity_test
1/1 Test #32: nodeos_sanity_test ...............   Passed    5.70 sec

100% tests passed, 0 tests failed out of 1

Total Test time (real) =   5.75 sec

[ghost]

WSL is untested and no surprise that you have issues.

WSL is community tested, there are endless "how-to" articles.

Having said this, the main problems are within:

• The tests themselves
• The documentation around the tests.

[ghost]

Not WSL, but (most possibly) a bug with relative paths, see #4765 (comment)