03:03:56 <gingeropolous> just plopped a self-built monerod into the xmrchain.net box.
16:00:58 <naughtyfox> hey guys! when next hardfork is gonna happen?
16:01:48 <moneromooo> Unknown.
16:03:00 <naughtyfox> thanks
17:11:29 <hyc> not this month or next, cetainly
17:58:20 <selsta> does anyone know how much space reproducible builds take up?
17:58:36 <gingeropolous> whats the thing we used before to collaborate on a statement?
17:58:44 <gingeropolous> or announcement or whatever
17:58:45 <selsta> including the downloaded dependencies
17:59:19 <selsta> gingeropolous: we can set a date once we know how long the CLSAG audit takes
18:00:16 <gingeropolous> well i think the general shift should be discussed. we don't need a hard date. I think the idea I've seen is to maintain a 6 month release schedule, with the possibility of a fork occurring at those releases
18:00:45 <gingeropolous> so any given 6 month date will either be a point release, or a major release
18:01:12 <gingeropolous> if there was ever any agreement that major release numbers related to consensus changes
18:01:16 <gingeropolous> i forget if that was the case.
18:02:37 <gingeropolous> because we've got a lot of people trained up on "ooh, its been six month, must be something going on"
18:03:41 <gingeropolous> they start seeing the seasons change, smell the air, days start drastically shifting duration, and they start thinkin there must be a fork a'coming
18:03:48 <hyc> I think my gitian tree is using about 12GB
18:04:10 <selsta> ty
18:04:34 <hyc> I'm not sure that that includes the space the docker containers themselves need
18:04:54 <hyc> seems to me that docker is storing those centrally, not in my gitianuser's home directory
19:22:15 <selsta> hyc: regarding macOS SDK, do I have to extract it?
19:22:28 <selsta> depends says extract, the other link says don’t
19:25:00 <selsta> ok looks like I don’t have to extract it
19:25:56 <selsta> gitian script does it for me
19:26:48 <scoobybejesus> indeed
19:27:37 <selsta> ok, started the build process now :D
19:41:56 <selsta> scoobybejesus: are you also going to build the reproducible builds? the more the better :)
19:50:13 <scoobybejesus> oh... probably...  :)   (i'm busy but will try to get it going real quick.. hopefully it cooperates)
19:50:41 <selsta> no hurry, I guess we will wait a few days before release anyway
19:50:48 <selsta> because we also have to build GUI
19:52:39 <iDunk> Looks like gcc got upgraded today from 7.4.0 to 7.5.0 in Ubuntu 18.04.
19:52:45 <iDunk> I'll rebuild.
19:53:20 <selsta> yep I’m currently using 7.5
20:49:37 <selsta> > cc1plus: out of memory allocating 65536 bytes after a total of 121749504 bytes
20:49:50 <moneromooo> So close...
20:49:53 <iDunk> i686 ?
20:50:04 <selsta> `./gitian-build.py --docker -j 4 --memory 6000 --detach-sign --no-commit --build selsta v0.15.0.5`
20:50:15 <selsta> should be ok for 8GB ram and 4 cores?
20:50:30 <moneromooo> -j4 for 8GB is really pushing it.
20:50:34 <asymptotically> i think some of the bigger files get upset with that
20:50:46 <selsta> ok back to j2 lol
20:50:53 <moneromooo> 3 might work if you don't get wallet2 and core_rpc_server at the same time :)
20:50:53 <iDunk> Which build ? Linux i686 or Win i686 ?
20:51:12 <iDunk> I use -j6 with -m10000.
20:51:55 <selsta> I think i686-linux-gnu
20:52:03 <selsta> but not sure where I can see that
20:52:31 <iDunk> builder/var/build.log
20:53:08 <selsta> https://paste.debian.net/hidden/2751be3d/
20:53:21 <selsta> the last lines
20:53:51 <selsta> I see both i686-linux-gnu and x86_64-linux-gnu
20:54:46 <iDunk> It's probably wallet2. My build will reach i686-linux-gnu soon and we'll see.
20:55:03 <selsta> can I simply restart?
20:55:15 <iDunk> Arrow up, enter :)
20:55:25 <selsta> ok, I changed the -j4 to -j2
20:55:32 <selsta> and enter :D
20:55:48 <iDunk> But since it didn't finish, it will probably start building deps again.
20:56:18 <selsta> looks like it
20:56:32 <selsta> > Memory usage:   274.5M out of 7.8G
20:56:41 <selsta> seems suspiciously low, but maybe it will rise once it builds monero
20:56:46 <iDunk> I don't think it's memory.
20:57:08 <selsta> that’s what my VM says
20:57:57 <iDunk> No, I mean it's a typical error for i686 builds of wallet2. Always on the edge of passing or failing.
20:58:48 <selsta> ah ok
20:58:58 <selsta> guess turning down the jobs can’t hurt
20:59:08 <iDunk> Hmm, looks like it's x86_64-linux-gnu after all.
20:59:24 <iDunk> My build completed that one.
20:59:53 <selsta> my host has 16GB ram and 4 cores, my VM has 8GB and 4 cores, should be ok?
21:00:23 <iDunk> You give 6000 MB to docker.
21:00:41 <iDunk> -j6 with -m10000 works here.
21:01:42 <scoobybejesus> so far so good?  https://paste.debian.net/1134370/
21:02:50 <iDunk> We'll see when my Linux build completes. Buids built with gcc 7.4.0 don't match.
21:04:46 <selsta> TheCharlatan hashes matched with yours iDunk, I asked him about GCC version
21:06:06 <iDunk> My Linux gcc 7.5.0 build match scoobybejesus'.
21:07:16 <iDunk> Bummer that a part of the toolchain got upgraded right after release.
21:39:20 <TheCharlatan> mine was still on 7.4 ... annoying. So lets all rebuild and bump to 7.5?
21:40:35 <iDunk> Any new build will be with 7.5.0, so might as well rebuild.
22:09:15 <scoobybejesus> fingers crossed we're good to go.  here's the whole thing: https://paste.debian.net/1134389/
22:31:02 <selsta> ok I’m close to the point where it failed previously
22:45:36 <selsta> no crash :)