a

[ghost]

No description provided.

[dexhunter]

I met the following error (also on ubuntu 1804)

76% tests passed, 10 tests failed out of 41

Label Time Summary:
long_running_tests    =   7.54 sec*proc (2 tests)

Total Test time (real) = 607.87 sec

The following tests FAILED:
	 31 - nodeos_sanity_test (Failed)
	 32 - nodeos_run_test (Failed)
	 34 - nodeos_run_test-mongodb (Failed)
	 35 - distributed-transactions-test (Failed)
	 36 - restart-scenarios-test-resync (Failed)
	 37 - restart-scenarios-test-hard_replay (Failed)
	 38 - restart-scenarios-test-none (Failed)
	 39 - validate_dirty_db_test (Failed)
	 40 - nodeos_sanity_lr_test (Failed)
	 41 - nodeos_voting_lr_test (Failed)
Errors while running CTest
Makefile:119: recipe for target 'test' failed
make: *** [test] Error 8

[dexhunter]

@lazaridiscom Any solutions yet?

[heifner]

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.

[dexhunter]

@lazaridiscom I got basically the same error

Test project /home/dex/github/eos/build
    Start 31: nodeos_sanity_test
1/1 Test #31: nodeos_sanity_test ...............***Failed    0.18 sec
 is not a valid path
 is not a valid path
 is not a valid path
 BEGIN
 UTC time: 2018-07-27 16:16:54.727825
 EOS Client version: 40a20769
 Processor: x86_64
 OS name: Linux-4.15.0-23-generic-x86_64-with-Ubuntu-18.04-bionic
SERVER: localhost
PORT: 8888
 cmd: pkill -9 keosd
 cmd: programs/eosio-launcher/eosio-launcher -k 9
 cmd: pkill -9 nodeos
Stand up cluster
  Checking if port 8888 is available.
  Checking if port 8889 is available.
 cmd: programs/eosio-launcher/eosio-launcher -p 1 -n 1 -s mesh -d 1 -i 2018-07-27T16:16:54.752 -f --p2p-plugin net --nodeos --max-transaction-time 5000 --abi-serializer-max-time-ms 5000 --filter-on * --p2p-max-nodes-per-host 1 --contracts-console
 ERROR: Launcher failed to launch.
 FAILURE - launcher
 ERROR: Failed to stand up eos cluster.
 Test failed.
   =================================================================
   Contents of etc/eosio/node_bios/config.ini:
   File etc/eosio/node_bios/config.ini not found.
   =================================================================
   Contents of var/lib/node_bios/stderr.txt:
   File var/lib/node_bios/stderr.txt not found.
  =================================================================
 == Errors see above ==
 Shut down the cluster.
  cmd: programs/eosio-launcher/eosio-launcher -k 9
  cmd: pkill -9 nodeos
 Shut down the wallet.
  cmd: pkill -9 keosd


0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.19 sec

The following tests FAILED:
	 31 - nodeos_sanity_test (Failed)
Errors while running CTest

[dexhunter]

I think the error is caused by missing files

    =================================================================
    Contents of etc/eosio/node_bios/config.ini:
    File etc/eosio/node_bios/config.ini not found.
    =================================================================
    Contents of var/lib/node_bios/stderr.txt:
    File var/lib/node_bios/stderr.txt not found.
   =================================================================

But I do not know how should I generate those files? Any ideas?

[heifner]

It is not that we wish newcomers to struggle. We have limited resources and this type of thing can really drain those resources. We are actively working on making the tests more resilient.

[heifner]

I imagine the sudo is suspect. That might be interfering with file creation/deletion and paths.

[heifner]

No hidden error-logs. Everything logs to stdout/stderr.

[taokayan]

is not a valid path => please set EOSIO_HOME to your build path.

[jgiszczak]

Abandoned and erased by original poster, and likely OBE.