Enable debug logging for core tests

[gr0vity-dev]

Failures on GitHub runners are sometimes hard to reproduce locally. Adding detailed logging helps analyze test failures directly from CI logs.

• Enables NANO_LOG_STATS and debug level logging for core tests across all CI platforms
• Helps diagnose intermittent test failures by providing more detailed execution traces

[gr0vity-dev-bot]

Test Results for Commit 71ed4dd

Pull Request 4807: Results
Overall Status: ❌

Test Case Results

• ✅ 5n4pr_conf_10k_bintree: PASS (Duration: 110s)
• ✅ 5n4pr_conf_10k_change: PASS (Duration: 182s)
• ✅ 5n4pr_conf_change_dependant: PASS (Duration: 128s)
• ✅ 5n4pr_conf_change_independant: PASS (Duration: 136s)
• ✅ 5n4pr_conf_send_dependant: PASS (Duration: 124s)
• ✅ 5n4pr_conf_send_independant: PASS (Duration: 131s)
• ✅ 5n4pr_rocks_10k_bintree: PASS (Duration: 114s)
• ✅ 5n4pr_rocks_10k_change: PASS (Duration: 175s)

Last updated: 2024-12-09 09:31:06 UTC

[pwojcikdev]

I wouldn't enable this, the amount of logs generated is just enormous to the point where it's not possible to easily see which tests failed anymore because github truncates viewable log size. An approach similar to gtest-parallel might be better where only log output from failed tests is printed.

[gr0vity-dev]

Oh right. when just running core_test without gtest-parallel, the output is always shown and will be huge. That's not what we want indeed!
Should we switch to gtest-parallel instead.
It will hide the output for all passing tests and just show failing tests.
We could set the --worker=1 so tests don't actually run in parallel

[pwojcikdev]

Gtest-parallel was added as a submodule in submodules/gtest-parallel so perhaps the script can invoke it from there

[pwojcikdev]

For some reason it no longer is able to show the sanitizer report https://github.com/nanocurrency/nano-node/actions/runs/12215820961/job/34078250929?pr=4807 It detects the problem, but the report is empty. Not sure what's going on here.