all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org, Mathieu Lirzin <mthl@gnu.org>
Subject: Re: guix weather issue? (was Re: guix package builds, subsitutes and --no-build)
Date: Tue, 26 Feb 2019 10:33:22 +0100	[thread overview]
Message-ID: <87imx651y5.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87zhqj81uj.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3683 bytes --]

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> writes:

> Giovanni Biscuolo <g@xelera.eu> writes:
>
>> do you think I should file a bug report or should I wait for more
>> investigation in this list?
>
> Let's confirm the issue by reproducing it, and then open a bug report.

OK, thanks!

> The possible issue here is that berlin reported a substitute was
> available, even though the substitute isn't actually available.
> Right?

AFAIU the issue is "guix weather" reporting on the availability related
to current master and not of user commit: am I wrong?

a little (digression

  anyway even if that is not the issue, users should have some way to
  check if a substitute is available for their current commit, so they
  can decide if they are willing to locally build or not.
    
  also, it would be useful if "guix package -i/-u" allowed users to
  choose to fail (via a flag or a CLI prompt) in case a substitute is
  not available; AFAIU "Substitution failure" [1] works when a
  substitute *is available* but download fails (and we have "--fallback"
  just in case), but there is non way to fail in case substitute in not
  available.
    
  in my specific case with ungoogled-chromium, it took about 8 hours on
  a 8 cores + 16GB RAM machine (although heavily used) to reach 75% of
  the build process... and finally I had to cancel the build since the
  machine load reached 40 (since other "heavy" processes started via
  cronjobs).)

anyway: back to the issue

> If you could provide the following information, I can try to reproduce
> it for you:
>
> - The output of 'guix describe'.
> - The manifest file you used in your 'guix weather' command.

I posted them yesterday in this thread; they are:

.ungoogled-chromium.manifest:

--8<---------------cut here---------------start------------->8---
(specifications->manifest
 '("ungoogled-chromium"))
--8<---------------cut here---------------end--------------->8---

--8<---------------cut here---------------start------------->8---
$ guix describe
Generation 3	Feb 19 2019 19:35:54	(current)
  guix a4fc802
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: a4fc80254a53b46b33f138d1009ddd044b8cb6be
--8<---------------cut here---------------end--------------->8---


yesterday I upgraded guix (guix pull), now I am on:

--8<---------------cut here---------------start------------->8---
Generation 4	feb 25 2019 16:21:26	(current)
  guix cc842b5
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: cc842b58af0a52dc8a01d4a4a30fa2fa0c599190
--8<---------------cut here---------------end--------------->8---

I was able to install ungoogled-chromium substitute:


today that package weather is the same as two days ago:

--8<---------------cut here---------------start------------->8---
$ guix weather --manifest=.ungoogled-chromium.manifest
computing 1 package derivations for x86_64-linux...
looking for 1 store items on https://ci.guix.info...
updating substitutes from 'https://ci.guix.info'... 100.0%
https://ci.guix.info
  100.0% substitutes available (1 out of 1)
  99,3 MiB of nars (compressed)
  288,3 MiB on disk (uncompressed)
  3,952 seconds per request (3,0 seconds in total)
  0,3 requests per second
  'https://ci.guix.info/api/queue?nr=1000' returned 504 ("Gateway Time-out")
--8<---------------cut here---------------end--------------->8---


Thanks!
Giovanni

[1]
https://www.gnu.org/software/guix/manual/en/html_node/Substitution-Failure.html#Substitution-Failure

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-02-26  9:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 16:39 guix package builds, subsitutes and --no-build Giovanni Biscuolo
2019-02-20 21:44 ` Leo Famulari
2019-02-21 15:14   ` ci.guix.info 504 gateway timeout (was Re: guix package builds, subsitutes and --no-build) Giovanni Biscuolo
2019-02-21 15:49     ` Ricardo Wurmus
2019-02-21 16:32       ` Mathieu Lirzin
2019-02-21 17:03         ` Giovanni Biscuolo
2019-02-21 18:29           ` Ricardo Wurmus
2019-02-22  4:46           ` Chris Marusich
2019-02-23 13:01         ` Alex Vong
2019-02-22  3:41     ` Chris Marusich
2019-02-25 13:11       ` Giovanni Biscuolo
2019-02-25 13:17         ` Ricardo Wurmus
2019-02-25 13:22           ` Ricardo Wurmus
2019-02-25 14:53             ` Giovanni Biscuolo
2019-02-25 15:10               ` Ricardo Wurmus
2019-02-25 15:37                 ` Mathieu Lirzin
2019-02-25 15:49                   ` Ricardo Wurmus
2019-02-25 16:18                     ` guix weather issue? " Giovanni Biscuolo
2019-02-26  7:07                       ` Chris Marusich
2019-02-26  9:33                         ` Giovanni Biscuolo [this message]
2019-02-27  7:29                           ` Chris Marusich
2019-02-27  8:21                             ` Giovanni Biscuolo
2019-02-27 17:53                               ` Chris Marusich
2019-02-27  8:26                             ` Björn Höfling
2019-03-03 16:06         ` ci.guix.info 504 gateway timeout " Mark H Weaver
2019-03-04 18:56           ` Leo Famulari
2019-02-25 19:13     ` swedebugia
2019-02-25 20:26       ` Giovanni Biscuolo
2019-02-25 20:31       ` Ricardo Wurmus
2019-02-25 20:46         ` Leo Famulari
2019-02-26 10:26           ` Giovanni Biscuolo

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=87imx651y5.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mthl@gnu.org \
    /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.