unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 49781@debbugs.gnu.org
Subject: bug#49781: Successful build on ci.guix not available as substitute
Date: Fri, 30 Jul 2021 12:11:17 +0200	[thread overview]
Message-ID: <87eebgjem2.fsf@gnu.org> (raw)
In-Reply-To: <87tukcyybm.fsf@inria.fr> ("Ludovic Courtès"'s message of "Fri, 30 Jul 2021 10:56:29 +0200")


Hello Ludo,

> It’s the first time I see this.  My understanding is that Cuirass makes
> a GET request on ‘guix publish’ upon build completion.  Could there be a
> race condition or something that can explain this?

Your understanding is correct :). However, looking at the
cuirass-remote-server.log file, I found:

--8<---------------cut here---------------start------------->8---
2021-07-29T22:31:48 fetching '/gnu/store/hrn9hj7v1img3il6afh3r036aczvwnyd-xnnpack-0.0-1.bbe8824.drv' from http://141.80.167.185:5558
2021-07-29T22:31:48 Failed to add /gnu/store/slm0x0j05vyl3vqbjhgc0nch6jca9fp3-xnnpack-0.0-1.bbe8824 to store.
--8<---------------cut here---------------end--------------->8---

There are quite a few other "Failed to add" traces in the log, and they
all seem to involve the machine behind the .185 IP address.

Fetching the substitute manually from Berlin works:

--8<---------------cut here---------------start------------->8---
 wget http://141.80.167.185:5558/nar/slm0x0j05vyl3vqbjhgc0nch6jca9fp3-xnnpack-0.0-1.bbe8824 --no-http-keep-alive
--8<---------------cut here---------------end--------------->8---

but using "ensure-path" fails this way:

--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> (set-build-options* s "http://141.80.167.185:5558")
$1 = #t
scheme@(guix-user)> (ensure-path s "/gnu/store/slm0x0j05vyl3vqbjhgc0nch6jca9fp3-xnnpack-0.0-1.bbe8824")
substitute: updating substitutes from 'http://141.80.167.185:5558'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
ERROR:
  1. &store-protocol-error:
      message: "path `/gnu/store/slm0x0j05vyl3vqbjhgc0nch6jca9fp3-xnnpack-0.0-1.bbe8824' does not exist and cannot be created"
      status: 1

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
--8<---------------cut here---------------end--------------->8---

Do you see any reason why ensure-path would fail while wget works?

Thanks,

Mathieu




  reply	other threads:[~2021-07-30 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  8:56 bug#49781: Successful build on ci.guix not available as substitute Ludovic Courtès
2021-07-30 10:11 ` Mathieu Othacehe [this message]
2021-08-02  8:38   ` Ludovic Courtès
2021-08-09 13:31     ` Mathieu Othacehe
2021-08-10  7:53       ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87eebgjem2.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=49781@debbugs.gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).