unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Frank Pursel <frank.pursel@gmail.com>
Cc: 58309@debbugs.gnu.org
Subject: bug#58309: [BUG Report] found a bug?
Date: Wed, 19 Oct 2022 12:48:14 +0200	[thread overview]
Message-ID: <86wn8wnl75.fsf_-_@gmail.com> (raw)
In-Reply-To: <878rlrn1d4.fsf@Ginko.local.mail-host-address-is-not-set> (Frank Pursel's message of "Fri, 07 Oct 2022 07:40:23 -0700")

Hi,

On Fri, 07 Oct 2022 at 07:40, Frank Pursel <frank.pursel@gmail.com> wrote:

> Running guix pull succeeded.  It isn't clear what changed to allow it to
> succeed when it had repeatedly failed over the past 48 hrs but this
> ticket should now be closed.  I am grateful for the hidden hands and/or
> magic that made this possible.

Thank you for your follow-up.

Hum, your both errors are weird.  The first one,

--8<---------------cut here---------------start------------->8---
 gnutls-3.7.2-doc  1.0MiB 659KiB/s 00:01 [###############   ]  84.1-Backtrace:
          18 (primitive-load "/gnu/store/8b0z5hm1kxha84g367yfshxjf1q4kka2-compute-guix-derivation")
In ice-9/eval.scm:

[...]

In ./guix/serialization.scm:
   102:11  1 (read-int #<input-output: file 10>)
     80:6  0 (get-bytevector-n* #<input-output: file 10> 8)

./guix/serialization.scm:80:6: In procedure get-bytevector-n*:
--8<---------------cut here---------------end--------------->8---

and the second one,

--8<---------------cut here---------------start------------->8---
guile-ssh-0.15.1-debug  238KiB 227.0MiB/s 00:00 [##################] 100.0%
Backtrace::
          15 (primitive-load "/gnu/store/k76q0ikk8a7769b0d2b9y3jj2mpaywh0-compute-guix-derivation")

[...]

In ./guix/store.scm:
  2050:12  4 (_ #<store-connection 256.99 7f65668495f0>)
  1402:13  3 (map/accumulate-builds #<store-connection 256.99 7f65668495f0> #<procedure 7f65618e48e0 at ./guix/stor?> ?)
   1398:5  2 (map/accumulate-builds #<store-connection 256.99 7f65668495f0> #<procedure 7f656a61b840 at ./guix/stor?> ?)
  1414:15  1 (_ #<store-connection 256.99 7f65668495f0> ("/gnu/store/063db2n6gr2pqvy77fxp82p0ki6vwklz-guile-avah?" ?) ?)
  1414:15  0 (loop #f)

./guix/store.scm:1414:15: In procedure loop:
--8<---------------cut here---------------end--------------->8---

Do you have issues with your store?  Maybe faulty?


Cheers,
simon

PS: Note you can close yourself the issue by replying to
58309-done@debbugs.gnu.org. :-)




  reply	other threads:[~2022-10-19 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 16:45 bug#58309: [BUG Report] found a bug? Frank Pursel
2022-10-05 17:58 ` bug#58309: [BUG Report] found a bug? followup Frank Pursel
2022-10-19 17:32   ` Maxime Devos
2022-10-20 14:11     ` Frank Pursel
2022-10-07 14:40 ` bug#58309: [BUG report] resolved Frank Pursel
2022-10-19 10:48   ` zimoun [this message]
2022-10-19 17:27 ` bug#58309: [BUG Report] found a bug? Maxime Devos
2023-01-11 22:16 ` bug#58309: [DONE] Frank Pursel

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=86wn8wnl75.fsf_-_@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=58309@debbugs.gnu.org \
    --cc=frank.pursel@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 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).