Hi Guix, It appears that the attatched derivation to build webkitgtk using the following guix ```Generation 2 Jun 26 2019 20:21:09 (current) guix ba91247 repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: ba912479e8481d69b699ce348b35d5d70f0c9367``` fails to build in a way that looks like a race. The suspicious lines in the attatched log are: ```Traceback (most recent call last): File "/tmp/guix-build-webkitgtk-2.24.2.drv-0/webkitgtk-2.24.2/Source/WebKit/Scripts/generate-message-receiver.py", line 28, in <module> import webkit.messagesEOFError: EOF read where object expected``` I have been able to sucessfully build webkitgtk on multiple hosts by using `-c 2` Best,Jack
The previously attatched log was generated with -c 12. I am currently running a build with -c 1 to verify that the problem occurs there as well. (I remember it happening with -c 1 in the past, but my memory could be faulty).
Today I was able to build webkitgkt 2.24.4 with Guix commit 4343eebfc9f7d44ec9a665f3374d1397301b542e. It looks like it is also available on ci.guix.gnu.org: https://ci.guix.gnu.org/25hz999kgcjh4alm6liwm12jm3blf5zz.narinfo This is a newer release of webkitgtk than the one that failed (2.24.2). Do we think this means that webkitgtk build problem has been fixed, or did we just get lucky with this release? My feeling is that we should close this bug and can open a new one if it re-occurs. Thoughts?Jack
(name . Jack Hill)(address . email@example.com)(address . firstname.lastname@example.org)
Hello, Jack Hill <email@example.com> skribis:
Toggle quote (13 lines)> Today I was able to build webkitgkt 2.24.4 with Guix commit> 4343eebfc9f7d44ec9a665f3374d1397301b542e. It looks like it is also> available on ci.guix.gnu.org:>> https://ci.guix.gnu.org/25hz999kgcjh4alm6liwm12jm3blf5zz.narinfo>> This is a newer release of webkitgtk than the one that failed> (2.24.2). Do we think this means that webkitgtk build problem has been> fixed, or did we just get lucky with this release?>> My feeling is that we should close this bug and can open a new one if> it re-occurs.
I agree. Closed! Thanks for following up on this,Ludo’.