-
Notifications
You must be signed in to change notification settings - Fork 175
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
Stuck on => [builder 13/20] RUN ./Engine/Build/BatchFiles/RunUAT.sh BuildGraph -target="Make Installed Build Linux" -script=Engine/Build/InstalledEngineBuild.xml -set:HostPlatformOnly=true #347
Comments
How much RAM/CPUs is allocated to Docker VM? |
50gb/16 CPUs/880gb disk |
One of the issues seems to be related to Multithreading, although this is really not my area of expertise. Output when running only one 1 CPU:
|
Given that you have plenty of RAM, it might possibly be easier to spin up a Linux VM and run ue4-docker inside it. |
When running only one CPU (which is also the default when doing the build in Hyper-V isolation on Windows) you may be bitten by an issue in the UE build system where the build management system keeps a whole CPU core busy checking for progress from the shader compiler processes, and hence the shader compiler processes themselves actually get little-to-no CPU time and don't progress, leading to an unexpected 10's-of-hours build. I only found this in UE4, I sent them a bug report, but I don't recall them accepting my fix (a sleep in the loop checking for Shader Compiler progress) or otherwise addressing it; a single-core development environment is not supported after all. In a multi-core environment, I couldn't demonstrate build-time improvement from my fix either, which surprised me. But that sounds like what you hit here in your single-CPU attempt. So maybe try with two cores, see if that avoids the compile hang and also the shader compiler issue. |
That error is Python seeing a Control-C in a thread, presumably because you're hitting Control-C to cancel the process, I don't believe it's related. |
Trying that right now, but first tests show that even in a UTM VM (Debian 12 Rosetta Virtualization) it still gets stuck. I will try an emulation later, but the performance is going to be horrendous. |
Emulation seems to be broken as well. Or at least it's unreasonable to use. Been "stuck" without progress on step [builder 11/20] for the past 8 hours, fans on full blast. |
We either run natively on Windows or on Linux. |
But only amd64 or does it work on linux arm? |
I think I found a "sort of" workaround for now. When step 13 fails, I run Only question is: How do I commit this stage manually to the layer to proceed to step 14? I could do a |
The only way you could use Can you use (Actually, you can use Oh, right, you can reproduce this in a My guess is that you've got all your cores busy-waiting, and no actual build processes are advancing. The fact that two-cores get stuck early suggests that this is the case, that the build is accumulating more busy-waiters over time, until they luck-out and fill all the available cores simultaneously. If that turns out to be the case, it may be possible to |
Output of the
ue4-docker info
command:Additional details:
ue4-docker build custom:UE532v0.0.1 -repo=https://github.com/dev-fredericfox/UnrealEngine_release.git -branch=main -username=dev-fredericfox -password=ghp_REDACTED --exclude templates --monitor
The
RUN ./Engine/Build/BatchFiles/RunUAT.sh BuildGraph -target="Make Installed Build Linux"
process just randomly stops at some point. Usually between 200/3994 and 600/3994, without any consistency or specified reason. It just keeps running without ever progressing.Example 01 Stuck at 234
Example 02 Stuck at 476:
The text was updated successfully, but these errors were encountered: