all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, Sjors Provoost <sjors@sprovoost.nl>
Cc: 58650@debbugs.gnu.org
Subject: bug#58650: build of /gnu/store/mw6ax0gk33gh082anrdrxp2flrbskxv6-openssl-1.1.1n.drv failed
Date: Thu, 3 Nov 2022 11:32:59 +0100	[thread overview]
Message-ID: <bfdb1591-d922-93d6-b2f8-12cd500925ca@telenet.be> (raw)
In-Reply-To: <86iljwbbj3.fsf@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1624 bytes --]



On 03-11-2022 11:03, zimoun wrote:
> Hi,
> 
> Thanks for the report.
> 
> On Wed, 19 Oct 2022 at 21:46, Sjors Provoost <sjors@sprovoost.nl> wrote:
>> Sorry if this is a duplicate or has already been fixed in a more recent commit.
>>
>> /builder for `/gnu/store/mw6ax0gk33gh082anrdrxp2flrbskxv6-openssl-1.1.1n.drv' failed with exit code 1
>> build of /gnu/store/mw6ax0gk33gh082anrdrxp2flrbskxv6-openssl-1.1.1n.drv failed
>> View build log at '/var/log/guix/drvs/mw/6ax0gk33gh082anrdrxp2flrbskxv6-openssl-1.1.1n.drv.gz'.
>> [...]
>>
>> ./guix/store.scm:1421:15: In procedure loop: [...]1).
> 
> It seems an error with the store.  Do you use the offload mechanism?
> And have you allowed the substitutes?

Looking at the attached build log, it is a build failure, not some store 
error:

Test Summary Report
-------------------
../test/recipes/80-test_ssl_new.t                (Wstat: 256 Tests: 29 
Failed: 1)
   Failed test:  12
   Non-zero exit status: 1
Files=158, Tests=2640, 66 wallclock secs ( 0.87 usr  0.07 sys + 56.47 
cusr  7.90 csys = 65.31 CPU)
Result: FAIL
make[1]: *** [Makefile:208: _tests] Error 1
make[1]: Leaving directory 
'/tmp/guix-build-openssl-1.1.1n.drv-0/openssl-1.1.1n'
make: *** [Makefile:205: tests] Error 2

Except for the different version number IIRC, I've noticed that one 
before (on core-updates).  That was without offloading and with 
substitutes, though the substitute servers didn't have a substitute 
available.

As the backtrace is a distraction, I propose merging something like 
<https://issues.guix.gnu.org/50238>.

Greetings,
Maxime

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-11-03 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 19:46 bug#58650: build of /gnu/store/mw6ax0gk33gh082anrdrxp2flrbskxv6-openssl-1.1.1n.drv failed Sjors Provoost
2022-11-03 10:03 ` zimoun
2022-11-03 10:32   ` Maxime Devos [this message]
2022-11-03 11:03     ` zimoun
2022-11-03 11:07     ` Sjors Provoost
2022-11-03 11:25       ` Sjors Provoost
2022-11-03 11:32         ` Maxime Devos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bfdb1591-d922-93d6-b2f8-12cd500925ca@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=58650@debbugs.gnu.org \
    --cc=sjors@sprovoost.nl \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.