Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep getting "exit status: 135" on "make check" step. #157

Open
betasauce opened this issue Oct 5, 2019 · 2 comments
Open

Keep getting "exit status: 135" on "make check" step. #157

betasauce opened this issue Oct 5, 2019 · 2 comments

Comments

@betasauce
Copy link

I am running ubuntu 18.04 and continually get "FAIL tests (exit status: 135)" being printed at random stages in the "make check" step each time I run it. I am seeing this in the "test-suite.log" file after running "make check" command. Here is just one example of output:

DEBUG :received command from node 4: inv
DEBUG :received command from node 2: inv
DEBUG :Statecheck: amount of connected nodes: 5
DEBUG :received command from node 4: inv
DEBUG :received command from node 8: headers
DEBUG :Got 2000 headers (took 0 s) from nodFAIL tests (exit status: 135)

I haven't been able to find what exit status 135 means (yet).

@xloem
Copy link
Collaborator

xloem commented Mar 26, 2021

make check seems to cut some output off the end. if this could be reproduced inside gdb or lldb the error would probably be visible.

$ make
$ gdb ./tests
(gdb) run
(gdb) bt

any output?

note: 135 appears to be SIGBUS, bus error.

@xloem xloem mentioned this issue Apr 5, 2021
@sergey-chernikov
Copy link

Failed tests (buffer overrun) might be fixed in #197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants