-
Notifications
You must be signed in to change notification settings - Fork 3.8k
last 6 tests failing #3842
Comments
I think that you use the server, am I right?? |
You might have copies of nodeos or keosd running in the background. If so,
you will need to kill these before running the tests.
…On Wed, Jun 6, 2018 at 2:59 AM, zhaokanghuiasd ***@***.***> wrote:
I think that you use the server, am I right??
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3842 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJsuzrA7_v96CUs-P5q2TdkWeUpXLy4_ks5t54vhgaJpZM4Ua6JJ>
.
|
not sure what you mean. I did something along the lines of
does that help? |
yes perhaps. Will have to wait until I am back in the office next week. Then I try again. Good hint. If that is the case, what about including a check-if-running into your test suite, to alert newbies like me? Only then I will be the last one having & reporting this issue. |
Im having something similar on mac, after 1.0 to 1.0.1 seems like validate_dirty_db_test is failing..
I did ./eosio_build.sh everything compiled fine.
ran
|
Gotcha. Redone, like this:
the result is the same though:
nope, sorry - the problem persists. |
Tried again with newer commit.Rebooted the Ubuntu VM, then rebuilt with newer code:
then
then the test
result now is
so even with a new commit ... 5 tests are failing. |
I get the same issue; was this resolved? |
28/45 Test #28: unit_test_binaryen ...................***Failed 10.92 sec |
yesterday's log file with errors was significantly larger, in particular, not the test of the node ended too unsuccessfully. I was able to create a wallet to import the key. but the node does not start, the log of its launch contains ./start.sh: line 22: ~/admin/eos/build/programs/nodeos/nodeos: No such file or d$ |
far test contains more errors 43/45 Test 43: nodeos_voting_lr_test ................***Failed 76.13 sec |
the same thing in the folder on the path admin / eos / build / programs / nodeos / nodeos is the file ... |
Total Test time (real) = 2039.24 sec The following tests FAILED: |
cd /path/to/eos |
28/46 Test #28: unit_test_binaryen ...................***Failed 9.41 sec |
Ubunt 18.04 |
ps -la |
f...k ................. /..... node! |
we fix the error of the head unit, the solution ./nodeos --delete-all-blocks --genesis-json genesis.json |
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD |
the best I |
did not understand you? thanks for the help ... :-P |
Addressed in #5525. |
HI! decided to update, problem again |
2018-09-12T08:24:35.384 thread-0 chain_plugin.cpp:556 plugin_initialize ] Starting up fresh blockchain with default genesis state. |
@Drug0j Your kernel is killing the process because it is trying to lock a great deal of memory. Update to v1.2.5, released yesterday. It reverts the memory locking behavior, which should allow your node to continue running. |
Hi my version 1.2.4 |
Here is the error that I now see quite often 2018-09-13T19:25:25.613 thread-0 controller.cpp:688 push_scheduled_trans ] 3050003 eosio_assert_message_exception: eosio_assert_message assertion failure |
Got myself an Ubuntu 18.04 VirtualBox now, because no Debian support yet.
Compilation took several hours, but it went through. Very happy. Soon I can try your tutorials.
However, not all tests are passing with 52da8d5:
full log of
./eosio_build.sh
The text was updated successfully, but these errors were encountered: