libera #monero-dev

26 Dec 2021

Official repo: github.com/monero-project/monero || Don’t ask to ask, just ask:) || Monero GUI dev is at #monero-gui || Monero website dev is at #monero-site || Non-dev questions -> #monero, please || No fork help, you’re on your own

• 11:41
  rbrunner
  I am a complete noob regarding what to do if GitHub tells me one of the tests failed
• 11:41
  rbrunner
  See here: github.com/monero-project/monero/ru…s/4635592269?check_suite_focus=true
• 11:42
  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?
• 11:51
  rbrunner
  Found "mining.py" in the meantime ...
• 11:53
  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'}
• 11:59
  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
• 12:02
  moneromooo
  I think this one existed before. Ignore if it it happened just once.
• 12:02
  moneromooo
  make -C build/..../tests/functional_tests test
• 12:02
  rbrunner
  Yeah, previous GitHub build before only small changes did not have that
• 12:16
  rbrunner
  Mining with interactive control in the daemon still works for me
• 15:37
  rbrunner
  They do mean that seriously that core_tests take hours ...
• 15:43
  moneromooo
  Run with MONERO_FASTER_POW=1
• 15:49
  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?
• 15:49
  rbrunner
  make -C build/..../tests/functional_tests test
• 15:50
  moneromooo
  You mean you don't want the C++ part to also run, depsite it taking like a second ?
• 15:51
  moneromooo
  Then: tests/functional_tests.py /usr/bin/python tests/functional_tests build/.../release all
• 15:53
  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 ...
• 15:53
  moneromooo
  Course not. Replace with the path on your filesystem.
• 15:54
  moneromooo
  Might be... build/Linux/master/release.
• 15:54
  moneromooo
  Depends on your OS and branch.
• 15:54
  rbrunner
  Ok, all clear. I'll try.
• 15:55
  moneromooo
  Or build/release if you build with the right env var.
• 15:55
  moneromooo
  Also, in the manual run above, you can replace all with the name of the test that interests you, like multisig maybe.
• 16:26
  rbrunner
  The "mining" functional tests run through on my machine repeatedly. So I will put that aside.
• 21:52
  selsta
  rbrunner: it's some obscure error that shows up on github ci every once in a while
• 21:52
  selsta
  it's unrelated to your changes and force pushing should make it green