all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: guix-pull prints stack trace
Date: Sat, 10 Sep 2016 12:33:46 +0200	[thread overview]
Message-ID: <87h99oqc1h.fsf@T420.taylan> (raw)
In-Reply-To: <877fakibfh.fsf@gmail.com> (Alex Vong's message of "Sat, 10 Sep 2016 13:14:10 +0800")

Alex Vong <alexvong1995@gmail.com> writes:

> Hello,
>
> It seems the commit c41d97b causes guix-pull to print stack trace.
>
> Here is the stack trace:
> ===========================================================================
> In ice-9/psyntax.scm:
>  989: 19 [scan ((define-module (gnu packages tex) #:use-module ...)) () ...]
>  279: 18 [scan ((#(syntax-object let # ...) (#) (# #) ...)) () ...]
> In ice-9/eval.scm:
>  411: 17 [eval # ()]
> In ice-9/boot-9.scm:
> 2951: 16 [define-module* (gnu packages tex) #:filename ...]
> 2926: 15 [resolve-imports ((# # license:) (#) (#) (#) ...)]
> 2864: 14 [resolve-interface (gnu packages pdf) #:select ...]
> 2789: 13 [#<procedure 84d300 at ice-9/boot-9.scm:2777:4 (name #:optional autoload version #:key ensure)> # ...]
> 3065: 12 [try-module-autoload (gnu packages pdf) #f]
> 2401: 11 [save-module-excursion #<procedure 5cedb40 at ice-9/boot-9.scm:3066:17 ()>]
> 3085: 10 [#<procedure 5cedb40 at ice-9/boot-9.scm:3066:17 ()>]
> In unknown file:
>    ?: 9 [primitive-load-path "gnu/packages/pdf" ...]
> In ice-9/eval.scm:
>  505: 8 [#<procedure 79a6a0 at ice-9/eval.scm:499:4 (exp)> (define-module # # ...)]
> In ice-9/psyntax.scm:
> 1106: 7 [expand-top-sequence ((define-module # # # ...)) () ((top)) ...]
>  989: 6 [scan ((define-module (gnu packages pdf) #:use-module ...)) () ...]
>  279: 5 [scan ((#(syntax-object let # ...) (#) (# #) ...)) () ...]
> In ice-9/eval.scm:
>  411: 4 [eval # ()]
> In ice-9/boot-9.scm:
> 2951: 3 [define-module* (gnu packages pdf) #:filename ...]
> 2926: 2 [resolve-imports ((# # license:) (#) (#) (#) ...)]
> 2867: 1 [resolve-interface (gnu packages javascript) #:select ...]
> In unknown file:
>    ?: 0 [scm-error misc-error #f ...]
>
> ERROR: In procedure scm-error:
> ERROR: no code for module (gnu packages javascript)
> builder for `/gnu/store/58ji3i7a0dl2sgf39m16l90alnyyvc9j-guix-latest.drv' failed with exit code 1
> guix pull: error: build failed: build of `/gnu/store/58ji3i7a0dl2sgf39m16l90alnyyvc9j-guix-latest.drv' failed
> ===========================================================================
>
> Looking at the patch, I think the problem is in
> `#:use-module (gnu packages javascript)'.

The bug I introduced to guix pull (while speeding it up) that has a tiny
chance of causing a thread race related error has never been fixed.
Maybe it's related to that.

As of e714797 I can't reproduce the error; guix pull runs fine to
completion.  Possibly a commit after c41d97b "fixed" the issue again by
changing the order of autoloads or some such.  But it could also be
related to the number of cores on my machine, how much you moved around
your pointer device recently, or the phase of the moon. :-\

If you still hit the error, or anyone else does, I'll get to work on it
ASAP.

Otherwise, I'm quite out of the loop but IIRC there was some talk of an
entirely different guix pull mechanism, that uses git pull or so?  If
so and if this bug continues to trigger extremely rarely, then I'm not
sure if it would be worth the effort to make bigger changes to the
current 'guix pull' mechanism.

Taylan


P.S.: Feel free to contact me on Freenode (nick 'taylan') if you want to
bypass email for quicker communication.

  reply	other threads:[~2016-09-10 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-10  5:14 guix-pull prints stack trace Alex Vong
2016-09-10 10:33 ` Taylan Ulrich Bayırlı/Kammer [this message]
2016-09-10 12:22   ` Alex Vong
2016-09-10 15:47 ` Leo Famulari

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=87h99oqc1h.fsf@T420.taylan \
    --to=taylanbayirli@gmail.com \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel@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.