-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build demos sequentially #4
base: main
Are you sure you want to change the base?
Conversation
That's weird. Both my computers have half that RAM and it does not crash with the current setup. Do notice that the current setup has this to prevent the build from crashing due to memory (which did happen without this in my I9). With this the most I observed during build was about 8GB used. I did not add sequential to the build process because it's so conservative. If we do use sequential, I recommend we remove the MAKEFLAGS variable from the environment. |
|
d0f56d0
to
dec3353
Compare
30850eb
to
f62d927
Compare
dec3353
to
49d5ee4
Compare
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
49d5ee4
to
7eb6544
Compare
Notice that I force pushed to this MR after squashing main. |
Alternatively, we could provide two build command aliases: the current one, plus another, sequential, for modest computers. |
Precisely what the title says.
beluga_demo_build
crashed my OS on build, and I have an i7 and 32GB worth of RAM.