-
Notifications
You must be signed in to change notification settings - Fork 3.6k
42/50 Test #42: validate_dirty_db_test ...............***Failed #6388
Comments
I did verify that the You can try being certain your environment is clean. Be sure no EOS.IO processes are running: pkill -9 eos to shut down any instances of nodeos, cleos, or keosd. Then root@hx-VirtualBox:/opt/eos/build# rm -r etc/eosio/node_bios
root@hx-VirtualBox:/opt/eos/build# rm -r etc/eosio/node_00
root@hx-VirtualBox:/opt/eos/build# rm -r var/lib/* to be sure no stray configuration files are left in the filesystem locations the tests use. The tests do these things themselves, so this is unlikely to solve the problem, but it doesn't hurt to be sure. Beyond that, try running the entire test suite again with |
I've tried, and I still have the same error, and I've reinstalled a virtual machine to verify it, but I still have the same problem (is there any configuration after installing the ubuntu-18.04.1-desktop version of the virtual machine)? I suspected that it was a virtual machine CPU concurrent problem, also doubted whether it was an IPv6 problem, have done experiments, but all reported the same error, now the error seems to be unable to obtain node information. |
The strangest part of this report is how all of your other tests pass. Your initial problem report showed complete success outside of the one failing test, yet many of the other tests do very similar things in terms of setup. Are you getting consistent passing results for all other tests? |
Support ticket with no response from submitter in 6 months; closing |
EOS version 1.4.4
system:ubuntu 18.04.1 LTS VirtualBox
CPU:i7 8750H
Memory:8G
DISK:50G
@jgiszczak Edited for clarity.
The text was updated successfully, but these errors were encountered: