-
Notifications
You must be signed in to change notification settings - Fork 3.8k
"make test" failed on centos7.5 #3729
Comments
@vchengsong The test suite requires python3. If you installed using the eosio_build.sh script then python3 is already installed. You must enable python3 prior to running make test. You can do so by running the following command: source /opt/rh/python33/enable |
@pacificcode how to do this on Mac OS? |
@ycryptx Python3 is installed by the eosio_build.sh script on Mac OS as well but you do not need to run any special commands to enable it. If you are running into issues with "make test" on Mac OS run the following and you should be good. cd /path/to/eos |
@pacificcode did that, my tests are still failing. Here's the log: 12% tests passed, 29 tests failed out of 33 Total Test time (real) = 660.44 sec The following tests FAILED: |
@ycryptx I would recommend you delete your current clone of the EOSIO repo and start over. verify python3which python3 | xargs ls -lah remove current EOSIO clonerm -rf /path/to/eos Start overgit clone https://github.com/EOSIO/eos.git --recursive Let me know how this works out for you |
@pacificcode Appreciate the help. I've done all the above, but am still encountering the same tests failed. running |
@ycryptx that absolutely is the issue. Would it be possible to run following commands and paste the entire output here? python3 -c 'import sys; print(sys.version_info.major)' 2>/dev/null |
Thanks again @pacificcode , but the problem persists. Did everything you mentioned there. Anything else I should try out? |
@ycryptx I need to see the output of running the commands above to advise correctly. |
I've attached a zip of my terminal shell @pacificcode |
@ycryptx thank you, that was very helpful. You can fix the issue you have been running into by running: brew install python@3 You should not need to recompile EOSIO (thats not absolutely, but you should be good on that one). After you install python3 cd into your eos/build directory and run: Let me know how that works out for you. |
@pacificcode this worked. Can't thank you enough! |
I build success on centos7.5, but run "make test" failed.
uname -a
Linux eos-hid-fn-2-2 3.10.0-862.2.3.el7.x86_64 #1 SMP Wed May 9 18:05:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
make test
Running tests...
Test project /opt/github/EOSIO/eos/build
Start 1: test_cypher_suites
1/33 Test #1: test_cypher_suites ..................... Passed 0.02 sec
Start 2: validate_simple.token_abi
2/33 Test #2: validate_simple.token_abi ..............***Failed 0.00 sec
Start 3: validate_eosio.token_abi
3/33 Test #3: validate_eosio.token_abi ...............***Failed 0.00 sec
Start 4: validate_eosio.msig_abi
4/33 Test #4: validate_eosio.msig_abi ................***Failed 0.00 sec
Start 5: validate_multi_index_test_abi
5/33 Test #5: validate_multi_index_test_abi ..........***Failed 0.00 sec
Start 6: validate_eosio.system_abi
6/33 Test #6: validate_eosio.system_abi ..............***Failed 0.00 sec
Start 7: validate_identity_abi
7/33 Test #7: validate_identity_abi ..................***Failed 0.00 sec
Start 8: validate_identity_test_abi
8/33 Test #8: validate_identity_test_abi .............***Failed 0.00 sec
Start 9: validate_stltest_abi
9/33 Test #9: validate_stltest_abi ...................***Failed 0.00 sec
Start 10: validate_exchange_abi
10/33 Test #10: validate_exchange_abi ..................***Failed 0.00 sec
Start 11: validate_test.inline_abi
11/33 Test #11: validate_test.inline_abi ...............***Failed 0.00 sec
Start 12: validate_hello_abi
12/33 Test #12: validate_hello_abi .....................***Failed 0.00 sec
Start 13: validate_asserter_abi
13/33 Test #13: validate_asserter_abi ..................***Failed 0.00 sec
Start 14: validate_infinite_abi
14/33 Test #14: validate_infinite_abi ..................***Failed 0.00 sec
Start 15: validate_proxy_abi
15/33 Test #15: validate_proxy_abi .....................***Failed 0.00 sec
Start 16: validate_test_api_abi
16/33 Test #16: validate_test_api_abi ..................***Failed 0.00 sec
Start 17: validate_test_api_mem_abi
17/33 Test #17: validate_test_api_mem_abi ..............***Failed 0.00 sec
Start 18: validate_test_api_db_abi
18/33 Test #18: validate_test_api_db_abi ...............***Failed 0.00 sec
Start 19: validate_test_api_multi_index_abi
19/33 Test #19: validate_test_api_multi_index_abi ......***Failed 0.00 sec
Start 20: validate_test_ram_limit_abi
20/33 Test #20: validate_test_ram_limit_abi ............***Failed 0.00 sec
Start 21: validate_eosio.bios_abi
21/33 Test #21: validate_eosio.bios_abi ................***Failed 0.00 sec
Start 22: validate_noop_abi
22/33 Test #22: validate_noop_abi ......................***Failed 0.00 sec
Start 23: validate_dice_abi
23/33 Test #23: validate_dice_abi ......................***Failed 0.00 sec
Start 24: validate_tic_tac_toe_abi
24/33 Test #24: validate_tic_tac_toe_abi ...............***Failed 0.00 sec
Start 25: validate_payloadless_abi
25/33 Test #25: validate_payloadless_abi ...............***Failed 0.00 sec
The text was updated successfully, but these errors were encountered: