00:33:34 <hyc> hi sorry I'm out all this weekend. sech1 were you able to kill the redundant cache flushes for this release?
07:17:50 <sech1> hyc no, it's still there. I don't think it hurts performance much, the benchmark showed more than 2200 h/s on M1
10:53:08 <selsta> riscv gitian fails here https://github.com/monero-project/monero/blob/master/src/common/compat/glibc_compat.cpp#L93
10:53:27 <selsta> glibc_compat.cpp:(.text+0x30): undefined reference to `glob_old'
10:54:00 <selsta> I thought about adding a similar line with `#elif defined(__riscv)` but don't know how to find the GLIBC version
11:52:56 <moneromoooo> external/db_drivers/liblmdb/mdb.c:#define       GLIBC_VER       ((__GLIBC__ << 16 )| __GLIBC_MINOR__)
11:56:00 <m-relay> <t​obtoht:monero.social> selsta: remove -DBACKCOMPAT=ON for riscv64 builds. glibc only added riscv support in 2.27
12:03:12 <selsta> thank you, trying that now
12:54:16 <selsta> tevador: can you test the if the gitian binary works on your risc-v system? https://github.com/selsta/monero/actions/runs/6597189374
13:06:20 <m-relay> <t​obtoht:monero.social> https://matrix.monero.social/_matrix/media/v1/download/monero.social/INAXBnvIykbDirAJSXyDcwjf
13:06:24 <m-relay> <t​obtoht:monero.social> :D
13:09:27 <selsta> nice :) now I just have to confirm that the hash stays consistent
13:38:21 <m-relay> <t​obtoht:monero.social> sent a test transaction with cli, seems to be working fine
13:38:43 <m-relay> <t​obtoht:monero.social> getting I/O errors with the daemon but this might be attributable to whatever F-tier sd card I'm running this on
13:44:05 <tevador> the monerod binary seems to be running fine
13:57:36 <sech1> Nice. Now we just need some RISC-V Raspberry Pi 5 level board
13:59:06 <selsta> if anyone else wants to confirm the hash, I tried with two separate Github Action VMs and they matched
13:59:08 <selsta> ./gitian-build.py --setup --docker --url https://github.com/selsta/monero github-actions riscv-gitian
13:59:23 <selsta> ./gitian-build.py --docker --detach-sign --no-commit --build -j 3 -o l --url https://github.com/selsta/monero github-actions riscv-gitian
13:59:34 <selsta> 688fd44ffa1dd27b8a48e2abc1ead1e0bfb048f6acd9e7ac97b200e2d3697b48  monero-riscv64-linux-gnu-c56932183.tar.bz2
14:02:12 <tevador> btw, monerod estimates 28 days to sync on my board... no sure how it compares to raspberry pis
14:06:26 <selsta> https://github.com/monero-project/monero/pull/9028
14:07:37 <m-relay> <t​obtoht:monero.social> selsta: looks good, just running a build to see if hash matches
14:21:36 <m-relay> <t​obtoht:monero.social> hash matches
14:21:59 <selsta> ty, also added the steps to check if hashes match in case someone else wants to try it
14:23:47 <plowsof> iirc the estimate can not see into the future, so its wildly inaccurate to begin with (it assume all blocks are emptyish in the beginning) but im not certain 
16:48:19 <hyc> hmm, lemme plug in a USB SSD so I have somewhere to store the blockchain
20:01:18 <hyc> hmm, my commit id was 9ea325777 for your PR. not c56932183
20:03:03 <hyc> so my build hash doesn't match yours
20:03:19 <hyc> selsta ^ where did your commit ID come from?
20:06:48 <hyc> ah I see. from your test branch
20:10:07 <hyc> ok trying again
20:10:21 <hyc> OPT="-o l -j8" ./dockrun.sh c56932183
20:19:00 <hyc> yeah hash matches
20:25:58 <hyc> started monerod
20:32:14 <hyc> sad. gigabit network, node traffic rarely hits 1Mbit
20:32:41 <hyc> this is syncing with --add-exclusive-node against my rockpro64. probably the rockpro is too slow
20:36:26 <moneromoooo> IIRC the node will download blocks till 100 MB, then wait to refill.
20:37:13 <hyc> yeah I doubt the 4GB RAM is enough for the rockpro to serve the tip of the chain and also replay from the beginningo f the chain for the new node
20:38:27 <hyc> so the final blocks should transfer quicker because they'll already be cached in memory