Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
The return of the "Generate precompilation as part of build process" #28319
So the first attempt of generating precompilation as part of build process went decent. It shows that this is likely the right thing to do since the latency of e.g. the REPL was noticeably better. However, the original PR #28118 had some problems, it caused #28316 and it also seems to get stuck on the build bots so I have opened a PR to revert it at #28318.
I'll use this PR to try other things and debug #28316.
What I changed here is that I am using a file to print stderr to in the spawned process in the hope that it will solve the deadlock in the buildbots. I also made the output slightly quieter and changed running
Buildbot running at https://build.julialang.org/#/builders/43/builds/1848.
Progress in the sense that the buildbot didn't hang but it seems to error in the same way as #28316 https://build.julialang.org/#/builders/43/builds/1848/steps/4/logs/stdio.
Added some debug stuff and reran the build bot.
Ok this prints on line 49348 (https://build.julialang.org/#/builders/43/builds/1849/steps/4/logs/stdio):
which seems like a weird handle?. Anyone know when that would happen?
Edit: Ok, using code that has the comment
could do it?
Let's try without that heh.
Jul 29, 2018
0 of 5 checks passed
Yes, Jameson explained what I did wrong (double initializing libuv which is a nono). In addition to the CI straight flush I also ran it on two buildbots (these failed 100% of the time before the libuv initialization fix) and they were both successful.
I think we should try this again.