From: Joshua Branson <jbranso@fastmail.com>
To: 33082@debbugs.gnu.org
Subject: bug#33082: guix pull resulted in an error: compute-guix-derivation
Date: Tue, 30 Oct 2018 11:15:08 -0400 [thread overview]
Message-ID: <87tvl3h3er.fsf@fastmail.com> (raw)
In-Reply-To: <CAE4v=pg2feYUnnP+g51PDPUSg-wTsG+S5V4ssB1skw-ukmjY0g@mail.gmail.com> ("Gábor Boskovits"'s message of "Tue, 30 Oct 2018 13:57:53 +0100")
Gábor Boskovits <boskovits@gmail.com> writes:
> Hello Joshua,
>
> Joshua Branson <jbranso@fastmail.com> ezt írta (időpont: 2018. okt.
> 30., K, 13:44):
>>
>> Gábor Boskovits <boskovits@gmail.com> writes:
>>
>> > Joshua Branson <jbranso@fastmail.com> ezt írta (időpont: 2018. okt. 29., H 15:54):
>> >
>> > ludo@gnu.org (Ludovic Courtès) writes:
>> >
>> > > Hello,
>> > >
>> >
>> > I was able to update successfully. This bug seems like a duplicate of
>> > python 2 not deterministic. Someone ought to close this bug report.
>> >
>> > I believe this is not the case, usually non deterministic means the build is not reproducible, while this is a
>> > non-deterministic test failure. I would suggest
>> > keeping this bug open, if I am right, maybe renaming to non-deterministic test failure in python2. What do you think?
>>
>> Fair enough. Since I made the bug report, then I should try to build it
>> again and see what happens.
>>
>
> Thanks for having a look, please make sure to use guix build -K, so
> that the failed build results are retained.
> If you can't trigger the failure, then I will try to do this later.
I was able to build this successfully:
guix build -K /gnu/store/qpvqn6ff2lmfq74ff3i9pz5hrb01p9hw-python2-2.7.14.drv
Collecting setuptools
Collecting pip
Installing collected packages: setuptools, pip
Successfully installed pip-9.0.1 setuptools-28.8.0
phase `install' succeeded after 32.6 seconds
starting phase `move-tk-inter'
phase `move-tk-inter' succeeded after 0.2 seconds
starting phase `remove-tests'
phase `remove-tests' succeeded after 0.8 seconds
starting phase `patch-shebangs'
phase `patch-shebangs' succeeded after 0.0 seconds
starting phase `make-libraries-writable'
phase `make-libraries-writable' succeeded after 0.1 seconds
starting phase `strip'
stripping binaries in "/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/lib" with "strip" and flags ("--strip-debug" "--enable-deterministic-archives")
stripping binaries in "/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/bin" with "strip" and flags ("--strip-debug" "--enable-deterministic-archives")
stripping binaries in "/gnu/store/z0r8jiimjgdg2sl3h9ad9z1v1i95752v-python2-2.7.14-tk/lib" with "strip" and flags ("--strip-debug" "--enable-deterministic-archives")
phase `strip' succeeded after 2.9 seconds
starting phase `validate-runpath'
validating RUNPATH of 64 binaries in "/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/lib"...
validating RUNPATH of 1 binaries in "/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/bin"...
validating RUNPATH of 1 binaries in "/gnu/store/z0r8jiimjgdg2sl3h9ad9z1v1i95752v-python2-2.7.14-tk/lib"...
phase `validate-runpath' succeeded after 1.1 seconds
starting phase `validate-documentation-location'
phase `validate-documentation-location' succeeded after 0.0 seconds
starting phase `delete-info-dir-file'
phase `delete-info-dir-file' succeeded after 0.0 seconds
starting phase `patch-dot-desktop-files'
phase `patch-dot-desktop-files' succeeded after 0.0 seconds
starting phase `install-license-files'
installing 1 license files
phase `install-license-files' succeeded after 0.0 seconds
starting phase `reset-gzip-timestamps'
phase `reset-gzip-timestamps' succeeded after 0.1 seconds
starting phase `compress-documentation'
compressing documentation in '/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/share/man' with "gzip" and flags ("--best" "--no-name")
phase `compress-documentation' succeeded after 0.1 seconds
successfully built /gnu/store/qpvqn6ff2lmfq74ff3i9pz5hrb01p9hw-python2-2.7.14.drv
/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14
/gnu/store/z0r8jiimjgdg2sl3h9ad9z1v1i95752v-python2-2.7.14-tk
I suppose now we can close this bug report, since I can't reproduce the
error?
Thanks
>
> Best regards,
> g_bor
next prev parent reply other threads:[~2018-10-30 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 14:58 bug#33082: guix pull resulted in an error: compute-guix-derivation Joshua Branson
2018-10-18 15:23 ` Gábor Boskovits
2018-10-19 9:11 ` Ludovic Courtès
2018-10-19 15:59 ` Joshua Branson
2018-10-19 17:09 ` Joshua Branson
2018-10-20 10:06 ` Ludovic Courtès
2018-10-29 15:09 ` Joshua Branson
2018-10-29 15:12 ` Gábor Boskovits
2018-10-30 12:59 ` Joshua Branson
2018-10-30 12:57 ` Gábor Boskovits
2018-10-30 15:15 ` Joshua Branson [this message]
2018-10-30 16:18 ` Gábor Boskovits
2018-10-30 17:12 ` Joshua Branson
2018-11-01 15:11 ` Ludovic Courtès
2019-02-28 10:09 ` bug#33082: Indeterministic test failure in python2 Gábor Boskovits
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=87tvl3h3er.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--cc=33082@debbugs.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 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).