-
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
-
mesaoptimizer
the default value was 1536M, and I changed it to 5536M
-
mesaoptimizer
So it *was* a heap issue, and compiling that file required more than 1.5G of heap space
-
selsta
.merges
-
xmr-pr
9023 9049 9052 9053 9056 9059 9060 9061
-
selsta
.merge+ 9079 9080 9069 9072 9073 9076 9077
-
xmr-pr
Added
-
mesaoptimizer
awww yes, the build succeeded!
-
mesaoptimizer
it feels so good to succeed at building the repo after so much effort
-
moneromooo
So the issue was just openbsd restricting core usage ?
-
mesaoptimizer
core usage? I think it was heap space, given my previous messages
-
moneromooo
Yes. That.
-
mesaoptimizer
I see. Well yeah, it was openbsd having low default limits for the heap size
-
moneromooo
You may want to update the OpenBSD section in the README.md with your changes then.
-
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
-
mesaoptimizer
ooh sweet
-
moneromooo
Actually, it might do the same.,,
-
mesaoptimizer
yeah... erm. I think I succeeded in building without reading this section
-
mesaoptimizer
I'm sorry
-
m-relay
<0xfffc:matrix.org> mesaoptimizer
-
m-relay
<ofrnxmr:monero.social> > No. Try the stack size limit increase. That should work, if it didn’t post the failure log.
-
m-relay
<ofrnxmr:monero.social> .
-
mesaoptimizer
the unit tests fail for me on the debug build
-
mesaoptimizer
one failed test: node_server.bind_same_p2p_port
-
moneromooo
Which line ?
-
mesaoptimizer
How do I figure out which line it is? I just ran `ctest` in the `build/debug/tests/unit_tests
-
moneromooo
I thought it'd mention it.
-
mesaoptimizer
Nope, it didn't -- the last few lines are
mesaoptimizer.com/test_failure.txt
-
moneromooo
Did you look at the test output above ?
-
mesaoptimizer
unfortunately my terminal trashed the output that would have contained this detail
-
mesaoptimizer
okay got it
-
mesaoptimizer
-
mesaoptimizer
seems like this may be an issue on my end, given that what is failing is an init() call
-
mesaoptimizer
okay, I ran `doas ifconfig lo0 alias 127.0.0.2` and reran the failing test and it succeeded
-
mesaoptimizer
I should probably add a relevant line to the file
-
mesaoptimizer
-
selsta
mesaoptimizer: do you have a github account?
-
selsta
otherwise I can submit the patch
-
mesaoptimizer
selsta: I do, I use the `mesaoptimizer0` github account when I need to use github
-
mesaoptimizer
I submitted the patch since I thought it would be easier than doing a fork + commit + pull request
-
mesaoptimizer
hash-slow-4 failed for `gmake release-test` due to segfault. Will investigate further tomorrow