selsta @hyc about how long did it take for the new gitian builds to complete ?

jeffro256[m]: it depends on how many cores you have, it took more than 6h for me with -j3

and it also depends if you have done a build previously

I was helping a friend compile Monero and they're getting `make[2]: *** [external/db_drivers/liblmdb/CMakeFiles/lmdb.dir/build.make:124: external/db_drivers/liblmdb/CMakeFiles/lmdb.dir/depend] Aborted (core dumped)` with no further context

I also don't see any open issues on this path. Anyone have any ideas?

Up to date Arch Linux for context, running make

probably running out of memory

try to make -j1

20 GB open, running with 4 threads, also tried 2, just had him try j1 and still has that error but now it's pointing to a panic in the c++ stdlib. It's probably some rolling problem, except they claim they rebooted after their most recent update (3 days ago) and can build Bitcoin without issue.

I think I've confirmed it's a rolling issue. Having him reboot, should fix it, no idea why j1 changed error presentation, thanks sech1 for being quick to help :)

start to finish, based on timestamps of my build/install logs, was 1 hour 10 minutes

using -j8

jeffro256[m]: that was nearly a full rebuild, since my package def updates meant most of the cached items had to be rebuilt

moneromooo: could you take a look at 8324? we added this for the malicious nodes but turns out it's possible that a legit node can send a peer list > 250

if they use tor / i2p

done

ty

moneromooo: this one too please monero-project/monero #8326

also small patch

Alright

@hyc which version was the target for the gitian ARM64 PR ?

I built for v0.17.3.2 and all my hashes are different

the PR itself was the target version

Ahhh that makes more sense

jeffro256[m]: you have to add `--url github.com/LMDB/bitmonero` and build `macarm2` branch

and you have to make sure that you get the correct gitian-build.py file from that branch

you don't need to change the URL, you can build the PR itself. it's the same hash.

git fetch origin pull/8312/head:pr8312; git checkout pr8312

@selsta Thanks, I'm currently running that build script I think I just ran it with the wrong target (v0.17.3.2)

Have you gotten this error befor?:

subprocess.CalledProcessError: Command '['git', 'checkout', 'macarm2']' returned non-zero exit status 1.

from the gitian build script

Which is weird because that's the branch I'm one right now, and I got there by doing `git checkout macarm2`

that's the steps i did, it seems to be possible too without changing the URL as hyc said but I didn't try that myself yet

Ah I was under the impression that dockrun.sh used the local branches instead of cloning the repo directly from the main project. That makes a lot more sense why it couldn't find the macarm2 branch

thanks for the help! I'll get back to you if/when the build completes

you can set the URL with dockrun too, just use "OPT=-u xxx" ./dockrun.sh ...

whatever's in $OPT is set when it invokes gitian-build.py