Runaway builds: the build hangs for 2 hours without producing any output on arm64

[yurivict]

The builds of the hyperswitch project hang for 120 minutes without any output on arm64.

This triggers the "runaway build" error in the FreeBSD package builder.

log

The Rust compiler should periodically print progress reports if/when it works on something for too long and no other printouts are occurring.

All recent rust versions are affected.

[Noratrieb]

That does sound like a hang, which is definitely a bug. Do you have any more information? Like the exact command and build config? This doesn't seem to be a universial issue when building this project given that people seem to develop it just fine.

[Noratrieb]

The Rust compiler should periodically print progress reports if/when it works on something for too long and no other printouts are occurring.

I'm not sure that's very useful, a bug is a bug, and I don't think prints would help that much with them.

[saethlin]

Agreed. The runaway build error is working as intended here, and we should not try to paper over it.

[yurivict]

This doesn't seem to be a universial issue when building this project given that people seem to develop it just fine.

Do they develop on arm64 though?

---

The easiest way to reproduce it is to run the FreeBSD VM on the arm64 machine and to build the
finance/hyperswitch port in it.

[saethlin]

Do they develop on arm64 though?

The project in question builds in 35 minutes on aarch64-unknown-linux-gnu.

[saethlin]

I'm interested in running down the cause of bonkers-long compile times, but this does not help:

The easiest way to reproduce it is to run the FreeBSD VM on the arm64 machine and to build the
finance/hyperswitch port in it.

I tried doing this. FreeBSD is extremely confusing to me as someone who has not used FreeBSD before, and I think you are misunderstanding how inaccessible FreeBSD is to those outside your community. My experience so far:

• You don't have sudo by default, I have to use su at least initially then pkg install things.
• My initial searching for how to build a port led me to some third-party explanation that was wrong. The relevant part of the actual docs is here: https://docs.freebsd.org/en/books/handbook/ports/#ports-using-installation-methods and the only relevant command is git clone --depth 1 https://git.FreeBSD.org/ports.git /usr/ports.
• You've already disabled the port in question, so building the port is not even as easy as cd /usr/ports/finance/hyperswitch then make. I've edited the Makefile to remove the line that mentions a runaway build. No idea if that's what I am supposed to do.
• I tried building this port but the entire thing is going single-threaded. I tried applying make -j32 but the Rust port doesn't build if I pass a -j flag to make. I've tried NUM_JOBS=32 make instead, it seems to work?
• When I finally got past the initial few steps of the port, the build kept putting up a TUI interface prompting me for options. Apparently I need to babysit ports?
• One of the TUI prompts asked me if I wanted to enable LTO for LLVM. It was unchecked by default. I don't know which kind of LTO that was, and it really matters for builds of LLVM and rustc.

The only way for someone to reproduce this is for you to share a foolproof explanation for how to do whatever your buildbot does. I'm pretty sure it isn't interacting with TUIs.