04:55:40 <jeffro256[m]> selsta @hyc about how long did it take for the new gitian builds to complete ?
13:11:26 <selsta> jeffro256[m]: it depends on how many cores you have, it took more than 6h for me with -j3
13:11:39 <selsta> and it also depends if you have done a build previously
14:16:55 <kayabaNerve> 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
14:17:06 <kayabaNerve> I also don't see any open issues on this path. Anyone have any ideas?
14:17:26 <kayabaNerve> Up to date Arch Linux for context, running make
14:18:59 <sech1> probably running out of memory
14:19:12 <sech1> try to make -j1
14:21:33 <kayabaNerve> 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.
14:23:09 <kayabaNerve> 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 :)
14:30:23 <hyc> start to finish, based on timestamps of my build/install logs, was 1 hour 10 minutes
14:30:33 <hyc> using -j8
14:32:33 <hyc> jeffro256[m]: that was nearly a full rebuild, since my package def updates meant most of the cached items had to be rebuilt
14:52:26 <MajesticExchange> https://github.com/moneroexamples/monero-compilation/blob/master/README.md
15:01:14 <selsta> 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
15:01:32 <selsta> if they use tor / i2p
15:05:55 <moneromooo> done
15:07:48 <selsta> ty
16:33:55 <selsta> moneromooo: this one too please https://github.com/monero-project/monero/pull/8326/
16:34:07 <selsta> also small patch
16:34:18 <moneromooo> Alright
16:43:39 <jeffro256[m]> @hyc which version was the target for the gitian ARM64 PR ?
16:44:00 <jeffro256[m]> I built for v0.17.3.2 and all my hashes are different
16:45:45 <hyc> the PR itself was the target version
16:46:24 <jeffro256[m]> Ahhh that makes more sense
16:49:37 <selsta> jeffro256[m]: you have to add `--url https://github.com/LMDB/bitmonero` and build `macarm2` branch
16:50:16 <selsta> and you have to make sure that you get the correct gitian-build.py file from that branch
16:54:03 <hyc> you don't need to change the URL, you can build the PR itself. it's the same hash.
16:54:32 <hyc> git fetch origin pull/8312/head:pr8312; git checkout pr8312
16:55:00 <jeffro256[m]> @selsta Thanks, I'm currently running that build script I think I just ran it with the wrong target  (v0.17.3.2)
16:55:24 <jeffro256[m]> Have you gotten this error befor?:
16:55:47 <jeffro256[m]> subprocess.CalledProcessError: Command '['git', 'checkout', 'macarm2']' returned non-zero exit status 1.
16:56:05 <jeffro256[m]> from the gitian build script
16:56:47 <jeffro256[m]> Which is weird because that's the branch I'm one right now, and I got there by doing `git checkout macarm2`
16:57:51 <selsta> https://paste.debian.net/hidden/83d79cf2/
16:58:19 <selsta> 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
17:12:39 <jeffro256[m]> 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 
17:19:40 <jeffro256[m]> thanks for the help! I'll get back to you if/when the build completes 
17:38:57 <hyc> you can set the URL with dockrun too, just use "OPT=-u xxx" ./dockrun.sh ...
17:39:28 <hyc> whatever's in $OPT is set when it invokes gitian-build.py