TBBle
commented
3 years ago We use --exclude debug builds here, and ue4 package shipping generally works. Perhaps this is the "framework is not valid" issue discussed in https://github.com/adamrehn/ue4-docker/pull/144#issuecomment-809844790, since it's a C# failure here, and the same problem seen by a UE 4.11 user was pointed towards toolchain installation issues. And there was an instance in 4.25.1 as well. Neither actually has an answer given though, so this might be a false lead. Your rebuild for stock ue4-docker should rule this in or out.
Also, https://github.com/adamrehn/ue4-docker/issues/99#issuecomment-716697043 saw the same failure when building with --exclude-debug, and that was building 4.25 with 0.0.71, which I'm pretty sure is what our most-recent container builds are using as well. Perhaps we haven't deployed the Windows images yet, I only know that we have the Linux builds active on CI, I don't know if the paired Windows images were tested after creation, as the relevant WCOW build node threw three disks in its RAID array and is being rebuilt.
So another theory: This is actually similar to https://github.com/adamrehn/ue4-docker/issues/141#issuecomment-808647324, and normally UE4Build.dll is generated during the engine build, before the PDBs are truncated by --exclude debug, but something in newer UE4 is causing UE4Build.dll to be rebuilt at ue4 package time. Perhaps the truncation changes the timestamp of a dependency, and so the UE4Build.dll is out-of-date compared to its source.
I suspect that we shouldn't be truncating C# PDBs with --exclude debug, just the C++ ones, since the C# compiler apparently tries to parse the existing PDB before it overwrites it.
slonopotamus
adamrehn
Output of the
ue4-docker infocommand:Additional details:
~I am actually running a modified version of
ue4-docker(see #144) but I think this issue is not related to my changes.~ This is ruled out, stock ue4-docker 0.0.81 produces exactly the same behavior.There is an independent report about the same issue with
4.25.3: https://github.com/adamrehn/ue4-docker/issues/99#issuecomment-716697043 by @Agendum.Way to reproduce
ue4-docker build 4.26.1 --no-engine --exclude ddc --exclude templates --exclude debugue4-docker test 4.26.1Expected
ue4-docker testpassesActual
I'm currently rerunning vanilla
ue4-dockerwithout my changes, but highly suspect that I will hit exactly the same error.Additional thoughts
This might be caused by
--exclude debug. Has anyone successfully passedue4-docker testusing an engine build with--exclude debug? Omiting--exclude debugis not an option for 4.26.1 because you'll hit #99. If this assumption is true, it would mean that--exclude debugis unusable and needs fixes.