-
rbrunner
I am a complete noob regarding what to do if GitHub tells me one of the tests failed
-
rbrunner
-
rbrunner
Is that in 'tests/functional_tests/functional_tests_rpc.py', and if yes, where, and how do I run that on my own machine?
-
rbrunner
Found "mining.py" in the meantime ...
-
rbrunner
... and found the error message in the output from GitHub: AssertionError: {'error': {'code': -1, 'message': "Couldn't stop mining due to unknown error."}, 'id': '0', 'jsonrpc': '2.0'}
-
rbrunner
This could have something to do with my changes, as I changed the tx pool, and mining needs of course a set of tx from that, but no idea how to properly debug that
-
moneromooo
I think this one existed before. Ignore if it it happened just once.
-
moneromooo
make -C build/..../tests/functional_tests test
-
rbrunner
Yeah, previous GitHub build before only small changes did not have that
-
rbrunner
Mining with interactive control in the daemon still works for me
-
rbrunner
They do mean that seriously that core_tests take hours ...
-
moneromooo
Run with MONERO_FASTER_POW=1
-
rbrunner
Ok, thanks. By the way, I could not yet figure out how to run the functional tests separately. Maybe in your hints from earlier today something is missing?
-
rbrunner
make -C build/..../tests/functional_tests test
-
moneromooo
You mean you don't want the C++ part to also run, depsite it taking like a second ?
-
moneromooo
Then: tests/functional_tests.py /usr/bin/python tests/functional_tests build/.../release all
-
rbrunner
"build/.../release" Do you mean this verbatim, with 3 dots, or do the 3 dots stand for some long path that I have to figure out? Forgive me if this is a dumb question ...
-
moneromooo
Course not. Replace with the path on your filesystem.
-
moneromooo
Might be... build/Linux/master/release.
-
moneromooo
Depends on your OS and branch.
-
rbrunner
Ok, all clear. I'll try.
-
moneromooo
Or build/release if you build with the right env var.
-
moneromooo
Also, in the manual run above, you can replace all with the name of the test that interests you, like multisig maybe.
-
rbrunner
The "mining" functional tests run through on my machine repeatedly. So I will put that aside.
-
selsta
rbrunner: it's some obscure error that shows up on github ci every once in a while
-
selsta
it's unrelated to your changes and force pushing should make it green