-
selstajeffro: monero-project/monero #8987 is causing some issues for me
-
selstajeffro256 (not sure if it tags you over the bridge), for example running `make release-test` now adds all this test data to the main dir that git shows as untracked files
-
selstabut the main issue is some tests are failing
-
selstafor example paste.debian.net/hidden/847d6010 - simply executing ./unit_tests makes this test fail, but executing it with lldb works, I assume that's because of the argc[0] in your code
-
selstabasically I have to run `unit_tests/unit_tests` instead of `./unit_tests`due to some path issue
-
selstaotherwise it doesn't find the test data
-
m-relay<jeffro256:monero.social> monero-project/monero #9045 should fix that
-
m-relay<jeffro256:monero.social> Sorry about that, I should have tested running `./unit_tests` from the current directory and the ctest suite
-
m-relay<jeffro256:monero.social> What's funny is that since I was running `./unit_tests` raw a lot from the source root, it actually had the exact opposite effect for me: it fixed adding untracked files to the source tree
-
m-relay<jeffro256:monero.social> Anyways, both issues should be fixed with that PR
-
m-relay<jeffro256:monero.social> Sorry about that
-
selstaty, will review
-
selstaalso did something in master change the result of the select_outputs.density test?
-
selstaExpected: (fabsf(selected_ratio - chain_ratio)) < (0.025f), actual: 0.0295275 vs 0.025
-
selstaI ran the test also locally yesterday and it was similarly out of range
-
selstacould be coincdence but in the past if it would fail it would be closer to 0.025 instead of 0.030
-
selstaappears to just have been coincidence, running the test locally 30 times made it fail once. ideally we would merge monero-project/monero #8024 and also add a deterministic test