Den mån 3 apr. 2023 kl 17:35 skrev Maxim Cournoyer < maxim.courno...@gmail.com>:
> Oh. This suggests your installation does not make use of the available > binary substitutes that would dramatically speed things up and > workaround the bug you encountered (which is caused by TLS certificates > expiring in the OpenSSL test suite, see: > https://issues.guix.gnu.org/56137). > I used the --no-substitutes argument as suggested. Maybe this is the reason? The substitute servers key should have been authorized at installation > by the guix-install.sh script, and Guix as of 1.4.0 uses both > 'https://ci.guix.gnu.org' and 'https://bordeaux.guix.gnu.org' as its > default substitute providers. > > What does 'cat /etc/guix/acl' show? It should have something like, the > first entry being Bordeaux and the second one for Berlin. > > --8<---------------cut here---------------start------------->8--- > (acl > (entry [...] ) > ) > --8<---------------cut here---------------end--------------->8--- > I have the same keys, only in opposite order. > 'guix weather openssl' should show it being available. I'd also like to > see the output of 'guix describe', to know from on which commit your > Guix is at. > dsg@dsg-ubuntu2210:~$ guix weather openssl hint: Consider installing the `glibc-locales' package and defining `GUIX_LOCPATH', along these lines: guix install glibc-locales export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale" See the "Application Setup" section in the manual, for more info. computing 1 package derivations for x86_64-linux... looking for 3 store items on https://ci.guix.gnu.org... https://ci.guix.gnu.org ☀ 100.0% substitutes available (3 out of 3) at least 11.4 MiB of nars (compressed) 32.6 MiB on disk (uncompressed) 0.977 seconds per request (2.9 seconds in total) 1.0 requests per second at least 1,000 queued builds aarch64-linux: 947 (94.7%) powerpc64le-linux: 51 (5.1%) i686-linux: 2 (.2%) build rate: 13.32 builds per hour i686-linux: 5.36 builds per hour x86_64-linux: 4.97 builds per hour aarch64-linux: 2.18 builds per hour powerpc64le-linux: 0.83 builds per hour armhf-linux: 0.04 builds per hour looking for 3 store items on https://bordeaux.guix.gnu.org... https://bordeaux.guix.gnu.org ☀ 100.0% substitutes available (3 out of 3) at least 7.8 MiB of nars (compressed) 32.6 MiB on disk (uncompressed) 0.244 seconds per request (0.7 seconds in total) 4.1 requests per second (continuous integration information unavailable) dsg@dsg-ubuntu2210:~$ guix describe hint: Consider installing the `glibc-locales' package and defining `GUIX_LOCPATH', along these lines: guix install glibc-locales export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale" See the "Application Setup" section in the manual, for more info. Generation 1 Apr 02 2023 09:27:21 (current) guix f0c8cb4 repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: f0c8cb44a4d912263025616bc921c011fcb1f0b4 If it isn't try with --substitute-urls; perhaps the default ones differ > for some reason: > --8<---------------cut here---------------start------------->8--- > guix weather openssl \ > --substitute-urls='https://bordeaux.guix.gnu.org https://ci.guix.gnu.org > ' > --8<---------------cut here---------------end--------------->8--- > In the meantime, I manually set the date/time to 2022-01-01 and that seemed to do the trick. The build completed successfully. In the Subversion build/test I see the same errors you have. I then did: [[[ $ guix build --no-substitutes --no-grafts --system=i686-linux --keep-failed subversion ... $ cd /tmp/guix-build-subversion-1.14.2.drv-0/ $ source environment-variables $ cd subversion-1.14.2 $ make check -j4 PARALLEL=4 ]]] This is now a functional environment to do more tests. I've been able to reproduce the error in this environment. If I did the same, without sourcing the environment variables (I had to make clean; ./config.nice before make), ie using the compiler and libraries included with the distribution, the tests succeed. I'm currently leaning towards something fishy with compiler/libraries used in guix. I'm trying to figure out exactly how this goes wrong, but threads programming is far from my comfort zone. In case anyone else would like to pick up, feel free! Kind regards, Daniel
