-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
OpenBSD/amd64 fails ringct unit tests #5568
Comments
Your log seems to be missing the interesting parts (the test failure(s)). |
It's my first day! :P Tell me exactly what you need from me. Is it another log file? Do I re-run the tests and paste the output? Thanks. |
build/wherever/tests/unit_tests/unit_tests.log. You can delete it first, so you only get one run logged. |
Running tests... 90% tests passed, 2 tests failed out of 20 Total Test time (real) = 3641.10 sec The following tests FAILED: |
$ ./functional_tests ... interesting.. this might have something to do with monerod becoming unstable after syncing all the blocks. |
Hmm, the interesting output doesn't get saved to that file :/ If by unstable you mean crash, get a stack trace (gdb /path/to/monerod /path/to/core, bt). |
Same for functional_tests: build/release/tests/functional_tests_rpc.py /usr/bin/python tests/functional_tests build/release all Adapt for python path and build path. Then post stdout/stderr. |
Okay, I'm running the tests again. By unstable I mean it appears to leak memory and consume the entire CPU. This seems to happen after the block syncing is done. I'm also looking into why the libunbound package on OpenBSD isn't built thread-safe. |
Okay, core_tests are passing now.. my loopback was firewalled.. my bad... :0 |
$ pwd ... and so on and so on... suggestions? |
Install the python requests module. |
ok.. new run... $ pwd A nice double-free in there somewhere.. hmm |
Run with -DSANITIZE=ON in cmake. I don't get that here. |
Any luck ? |
Unfortunately After some manual debugging I found the double free cause. Here the monero/src/cryptonote_basic/miner.cpp Line 374 in 51766d0
The destructor of |
I think it's all good now, is it ? |
Yes. All 20 tests pass for me. PR #5679 fixes a tests generation issue. |
Thanks. +resolved |
Anyone well-versed with ringct who can point me in the right direction to get this fixed on OpenBSD/amd64?
Preview below.. full file compressed and attached as well.
unit_tests.log.gz
2019-05-22 21:19:14.138 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:698 genRct is not suitable for 2+ rings
2019-05-22 21:19:14.798 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:476 Empty pubs
2019-05-22 21:19:14.798 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:754 Empty inamounts
2019-05-22 21:19:14.799 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:476 Empty pubs
2019-05-22 21:19:14.799 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:754 Empty inamounts
2019-05-22 21:19:14.859 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:476 Empty pubs
2019-05-22 21:19:14.860 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:754 Empty inamounts
2019-05-22 21:19:17.627 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:698 genRct is not suitable for 2+ rings
2019-05-22 21:19:17.681 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:698 genRct is not suitable for 2+ rings
2019-05-22 21:19:17.735 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:698 genRct is not suitable for 2+ rings
2019-05-22 21:19:20.730 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:698 genRct is not suitable for 2+ rings
2019-05-22 21:19:20.784 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:698 genRct is not suitable for 2+ rings
2019-05-22 21:19:21.140 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:918 Mismatched sizes of outPk and rv.p.rangeSigs
2019-05-22 21:19:21.186 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:918 Mismatched sizes of outPk and rv.p.rangeSigs
2019-05-22 21:19:21.231 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:918 Mismatched sizes of outPk and rv.p.rangeSigs
2019-05-22 21:19:21.276 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:920 full rctSig has not one MG
2019-05-22 21:19:21.362 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:281 Bad rv.ss size
2019-05-22 21:19:21.451 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:281 Bad rv.ss size
2019-05-22 21:19:21.538 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:281 Bad rv.ss size
2019-05-22 21:19:21.624 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:283 rv.ss is not rectangular
2019-05-22 21:19:21.711 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:283 rv.ss is not rectangular
2019-05-22 21:19:21.797 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:283 rv.ss is not rectangular
2019-05-22 21:19:21.883 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:280 Bad II size
2019-05-22 21:19:21.970 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:280 Bad II size
2019-05-22 21:19:22.056 0xfc8bd4facc0 ERROR ringct src/ringct/rctSigs.cpp:280 Bad II size
[SNIP]
The text was updated successfully, but these errors were encountered: