my daemon is stuck on 2569430

no wait, sorry

A small announcement:... (full message at libera.ems.host/_matrix/media/r0/do…aae4e6bb4e254947f9a8704777242ae0ef9)

Hello. I am/have been having a wierd issue where my funds dont show up in the gui wallet, connected with a ledger. Have been trying to find a solution since may last year with no success. I have tried everything I myself could find on the web as a solution, but nothing has worked. Is there anyone here that can help me/knows what my issue is (if so I could explain it further)? Would greatly appreciate any help since I don’t know

where else to turn. Thank you.

Try asking in #monero.

well, what i believe to be is master branch on xmrchain has been up for 81d 14h 14m 2s

hrm. compiling master makes monerod help spit out (v0.17.0.0-4f6e17ad8)

well in any case xmrchain.net is now running master

at least for mainnet

How do I run all the tests ?

(the ones that run during the ubuntu CI build)

make -C build/etc test

Awesome, thank you so much!

Are the tests (specifically core_tests) fail-fast?

No.

Well, depends on your subjective subjevtivity I subjectively surmise.

"Fail fast" usually means "if bad, say so quick". But it's a test. If it's bad, and it says so quick, why would it continue for a while just to say it went well ?

Normal programs would use that time to produce useful data, etc. A test doesn't. It just says yes/no.

i see a lot of "generate" stuff going on in some tests. i wonder if any of that stuff can be pre-generated and loaded from a fixture file?

See --help. It's probably broken though, feel free to fix it if you can.

Also, caching means you're in danger of using stale data. Be wary of this.

By --help, I mean core_tests --help.

But tbh, it's not too long if you use the quick PoW env var.

"not too long" adds up over hundreds or thousands of tests :)

my knowledge of this stuff comes from an entirely different language so im just spitballing here for jeffro

luigi1111: merges? pls

Probably

moneromooo I guess I meant to ask if a subtest of (for example) core_tests fails, will core_tests continue to test the rest of the subtests in core_tests? Because overall, that isn't true of all the tests correct? Like if unit_tests fails, the hash_fast test will still run, right? But conversely, if a subtest of any of hash-target, core_tests, etc fail then that specific test terminates with a failure immediately right?

Sorry if its a dumb question

imo fast-fail should be a user option, turned on for CI runs since there you only care that anything failed rather than a full list of fails

core_tests will run all tests, whether or not any of them fail.

Same for unit_tests.

If a (core, unit other) test fails, other will also run.

For core tests, since they're a bit long and spammy, you can grep '#TEST#' in the log, to see fail/success as they run.

Then you can strt debugging a failing one as the rest runs.

.merges

moneromooo: anything they can provide to debug this? monero-project/monero #8194

as expected, the OS update didn't fix it

so... possibly not related at all since user's details dont match mine, but i had similar symptoms when i tried my first sync. i am hosting the blockchain on a NAS while daemon runs on my server. the NAS had some goofy-ass software that "indexed" things every time a change was made on disk. this basically caused the sync to grind to a halt somewhere around the same block height user is mentioning. once i was able to turn that

nonsense off, sync finished cleanly

guess I'll try a fresh blockchain sync to check if I can reproduce

but we didn't get any other reports about this

a lot of random forum posts out there insist that this is just what happens on non-SSDs, which is total nonsense, so i think a lot of people just give up

HDDs are significantly slower for sync

my problem was the NAS' software doesnt give you any easy way to remove this index shit so all of my time was spent figuring out how to do that

yeah but they shouldnt grind to a halt. after cleaning out the crap software it took me 1.5 days for full sync

and thats HDD over a network drive with RAID