00:14:38 <mesaoptimizer> success. I increased `:datasize-cur:` and `:datasize-max:` in /etc/login.conf for the `default` and `staff` classes so it applied to my user, which I verified using `ulimit -a`, and then that specific cpp file succeeded in getting built
00:15:12 <mesaoptimizer> the default value was 1536M, and I changed it to 5536M
00:15:44 <mesaoptimizer> So it *was* a heap issue, and compiling that file required more than 1.5G of heap space
04:05:46 <selsta> .merges
04:05:46 -xmr-pr- 9023 9049 9052 9053 9056 9059 9060 9061
04:08:23 <selsta> .merge+ 9079 9080 9069 9072 9073 9076 9077
04:08:23 <xmr-pr> Added
10:31:23 <mesaoptimizer> awww yes, the build succeeded!
10:31:40 <mesaoptimizer> it feels so good to succeed at building the repo after so much effort
10:31:59 <moneromooo> So the issue was just openbsd restricting core usage ?
10:32:40 <mesaoptimizer> core usage? I think it was heap space, given my previous messages
10:32:53 <moneromooo> Yes. That.
10:33:16 <mesaoptimizer> I see. Well yeah, it was openbsd having low default limits for the heap size
10:34:02 <moneromooo> You may want to update the OpenBSD section in the README.md with your changes then.
10:34:09 <mesaoptimizer> and I increased it as described above, by changing `:datasize-cur:` (important!) in `/etc/login.conf` such that my `ulimit -a` specified I had 5G instead of 1G of heap size
10:34:19 <mesaoptimizer> ooh sweet
10:35:29 <moneromooo> Actually, it might do the same.,,
10:36:30 <mesaoptimizer> yeah... erm. I think I succeeded in building without reading this section
10:36:41 <mesaoptimizer> I'm sorry
11:26:02 <m-relay> <0​xfffc:matrix.org> mesaoptimizer
12:39:22 <m-relay> <o​frnxmr:monero.social> > No. Try the stack size limit increase. That should work, if it didn’t post the failure log. 
12:39:23 <m-relay> <o​frnxmr:monero.social> .
15:21:52 <mesaoptimizer> the unit tests fail for me on the debug build
15:22:17 <mesaoptimizer> one failed test: node_server.bind_same_p2p_port
15:31:53 <moneromooo> Which line ?
15:32:40 <mesaoptimizer> How do I figure out which line it is? I just ran `ctest` in the `build/debug/tests/unit_tests
15:33:10 <moneromooo> I thought it'd mention it.
15:36:24 <mesaoptimizer> Nope, it didn't -- the last few lines are https://mesaoptimizer.com/test_failure.txt
15:44:09 <moneromooo> Did you look at the test output above ?
15:45:10 <mesaoptimizer> unfortunately my terminal trashed the output that would have contained this detail
15:45:47 <mesaoptimizer> okay got it
15:47:30 <mesaoptimizer> line 324 and 327 based on https://mesaoptimizer.com/LastTest.log
15:48:08 <mesaoptimizer> seems like this may be an issue on my end, given that what is failing is an init() call
15:57:34 <mesaoptimizer> okay, I ran `doas ifconfig lo0 alias 127.0.0.2` and reran the failing test and it succeeded
15:59:23 <mesaoptimizer> I should probably add a relevant line to the file
16:26:43 <mesaoptimizer> here's a patch to document this fix: https://mesaoptimizer.com/0001-OpenBSD-node-server-fix-IP-localhost-by-aliasing.patch
18:06:09 <selsta> mesaoptimizer: do you have a github account?
18:06:17 <selsta> otherwise I can submit the patch
18:06:59 <mesaoptimizer> selsta: I do, I use the `mesaoptimizer0` github account when I need to use github
18:07:42 <mesaoptimizer> I submitted the patch since I thought it would be easier than doing a fork + commit + pull request
21:10:07 <mesaoptimizer> hash-slow-4 failed for `gmake release-test` due to segfault. Will investigate further tomorrow