guix-1.1.0-13.26611f5 fails to build

  • Done
  • quality assurance status badge
Details
5 participants
  • Ludovic Courtès
  • Mathieu Othacehe
  • Mathieu Othacehe
  • Ricardo Wurmus
  • zimoun
Owner
unassigned
Submitted by
Mathieu Othacehe
Severity
important
Merged with

Debbugs page

M
M
Mathieu Othacehe wrote on 1 Jul 2020 00:09
(address . bug-guix@gnu.org)(address . janneke@gnu.org)
87y2o3zp7n.fsf@gnu.org
Hello,

There are two test failures on berlin during guix-1.1.0-13.26611f5
tests. Log attached!

Thanks,

Mathieu
Attachment: log.gz
M
M
Mathieu Othacehe wrote on 1 Jul 2020 00:45
(address . 42148@debbugs.gnu.org)
87r1tvznjh.fsf@gnu.org
Toggle quote (3 lines)
> There are two test failures on berlin during guix-1.1.0-13.26611f5
> tests. Log attached!

Note that on my own machine, I cannot reproduce this issue.

Mathieu
L
L
Ludovic Courtès wrote on 1 Jul 2020 15:11
(name . Mathieu Othacehe)(address . othacehe@gnu.org)(address . 42148@debbugs.gnu.org)
87a70iyjf8.fsf@gnu.org
Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

Toggle quote (3 lines)
> There are two test failures on berlin during guix-1.1.0-13.26611f5
> tests. Log attached!

The actual build failure concerns code that hasn’t change in recent
years:

Toggle snippet (21 lines)
test-name: filtered-port, file
location: /tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source/tests/utils.scm:146
source:
+ (test-assert
+ "filtered-port, file"
+ (let* ((file (search-path %load-path "guix.scm"))
+ (input (open-file file "r0b")))
+ (let*-values
+ (((compressed pids1)
+ (filtered-port `(,%gzip "-c" "--fast") input))
+ ((decompressed pids2)
+ (filtered-port `(,%gzip "-d") compressed)))
+ (and (every (compose zero? cdr waitpid)
+ (append pids1 pids2))
+ (equal?
+ (get-bytevector-all decompressed)
+ (call-with-input-file file get-bytevector-all))))))
actual-value: #f
result: FAIL

However, the log also shows that something’s wrong with time on that
machine:

Toggle snippet (46 lines)
starting phase `check'
make: guix/store/schema.sql: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make: Warning: File 'guix/store/schema.sql' has modification time 15586324043 s in the future
GEN nix/libstore/schema.sql.hh
make check-recursive
make[1]: Entering directory '/tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source'
Making check in po/guix
make[2]: Entering directory '/tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source/po/guix'
make[2]: Leaving directory '/tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source/po/guix'
Making check in po/packages
make[2]: Entering directory '/tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source/po/packages'
make[2]: Leaving directory '/tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source/po/packages'
make[2]: Entering directory '/tmp/guix-build-guix-1.1.0-13.26611f5.drv-0/source'
make[2]: guix/store/schema.sql: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: Warning: File 'guix/store/schema.sql' has modification time 15586324043 s in the future
GEN nix/libstore/schema.sql.hh
CXX nix/libstore/libstore_a-local-store.o
AR libstore.a
ar: `u' modifier ignored since `D' is the default (see `U')
CXXLD guix-daemon
make[2]: guix/base16.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/base32.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/cpio.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/pki.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/memoization.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/sets.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/monad-repl.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999
make[2]: guix/glob.scm: Timestamp out of range; substituting 2514-05-30 01:53:03.999999999

[...]

Compiling Scheme modules...
[ 1%] LOAD guix/base16.scm
[ 1%] LOAD guix/base32.scm
[ 2%] LOAD guix/cpio.scm
[ 3%] LOAD guix/pki.scm
[ 3%] LOAD guix/memoization.scm
[ 4%] LOAD guix/sets.scm
[ 5%] LOAD guix/monad-repl.scm
[ 5%] LOAD guix/glob.scm
[ 6%] LOAD guix/workers.scm
[ 7%] LOAD guix/zlib.scm
[ 7%] LOAD guix/build-system.scm
[ 8%] LOAD guix/build-system/android-ndk.scm

I suspect that weird timestamp issue could well explain many things.

Ludo’.
M
M
Mathieu Othacehe wrote on 2 Jul 2020 00:00
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 42148@debbugs.gnu.org)
87366ae705.fsf@gnu.org
Hey!

Toggle quote (8 lines)
> [ 5%] LOAD guix/glob.scm
> [ 6%] LOAD guix/workers.scm
> [ 7%] LOAD guix/zlib.scm
> [ 7%] LOAD guix/build-system.scm
> [ 8%] LOAD guix/build-system/android-ndk.scm
>
> I suspect that weird timestamp issue could well explain many things.

Oh good catch, I didn't notice it. All build machines seem to have a
sane "date" output, but I guess the issue is probably trickier. For now,
I'll make a new Guix update to trigger a new rebuild and try to find the
guilty machine in parallel.

Thanks,

Mathieu
M
M
Mathieu Othacehe wrote on 3 Sep 2020 04:54
control message for bug #38958
(address . control@debbugs.gnu.org)
878sdrdqjc.fsf@cervin.i-did-not-set--mail-host-address--so-tickle-me
merge 38958 42148
quit
L
L
Ludovic Courtès wrote on 16 Sep 2020 12:57
(address . control@debbugs.gnu.org)
871rj1mr3v.fsf@gnu.org
severity 38958 important
quit
Z
Z
zimoun wrote on 22 Mar 2021 06:07
Re: bug#42148: guix-1.1.0-13.26611f5 fails to build
(name . Mathieu Othacehe)(address . othacehe@gnu.org)
8735wncp5t.fsf@gmail.com
Hi,

On Wed, 01 Jul 2020 at 09:09, Mathieu Othacehe <othacehe@gnu.org> wrote:

Toggle quote (3 lines)
> There are two test failures on berlin during guix-1.1.0-13.26611f5
> tests. Log attached!

What is the status of this bug#42148? From my understanding, it could
be closed. Right?


Cheers,
simon
R
R
Ricardo Wurmus wrote on 15 Jun 2022 23:34
guix-1.1.0-13.26611f5 fails to build
(address . 42148-done@debbugs.gnu.org)
87pmj9xgib.fsf@elephly.net
Closing, because this is no longer relevant.

--
Ricardo
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 42148@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 42148
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch