failing test-suite

  • Done
  • quality assurance status badge
Details
2 participants
  • Martin Castillo
  • Ludovic Courtès
Owner
unassigned
Submitted by
Martin Castillo
Severity
normal
M
M
Martin Castillo wrote on 16 Feb 2018 01:02
(address . bug-guix@gnu.org)
ac623b1c-57f1-cfc1-b090-66cf14191800@uni-bremen.de
on my raspberry pi, building from commit
7e0a6fac0b4ebffda322eff6e803363ee72a257a. the test-suite fails.

my current guix is from november or so.
the first log was created with -j 4.
the second with -j 1.

not sure, how critical the errors are. somehow i still can't read the
test-suite logs.
L
L
Ludovic Courtès wrote on 16 Feb 2018 10:39
(name . Martin Castillo)(address . castilma@uni-bremen.de)(address . 30476@debbugs.gnu.org)
873721s27b.fsf@gnu.org
Hi Martin,

Martin Castillo <castilma@uni-bremen.de> skribis:

Toggle quote (7 lines)
> on my raspberry pi, building from commit
> 7e0a6fac0b4ebffda322eff6e803363ee72a257a. the test-suite fails.
>
> my current guix is from november or so.
> the first log was created with -j 4.
> the second with -j 1.

You forgot to attach the logs. :-)

Ludo’.
M
M
Martin Castillo wrote on 16 Feb 2018 12:51
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 30476@debbugs.gnu.org)
40111d94-43df-1c0d-3cdb-36b8cf99b0cc@uni-bremen.de
On 16.02.2018 10:39, Ludovic Courtès wrote:
Toggle quote (13 lines)
> Hi Martin,
>
> Martin Castillo <castilma@uni-bremen.de> skribis:
>
>> on my raspberry pi, building from commit
>> 7e0a6fac0b4ebffda322eff6e803363ee72a257a. the test-suite fails.
>>
>> my current guix is from november or so.
>> the first log was created with -j 4.
>> the second with -j 1.
>
> You forgot to attach the logs. :-)

How embarrassing.
Attachment: pi-test-suite.log
Attachment: pi-test-suite3.log
L
L
Ludovic Courtès wrote on 16 Feb 2018 14:00
(name . Martin Castillo)(address . castilma@uni-bremen.de)(address . 30476@debbugs.gnu.org)
878tbtozrv.fsf@gnu.org
Martin Castillo <castilma@uni-bremen.de> skribis:

Toggle quote (11 lines)
> ++ guix build superseded -d
> accepted connection from pid 22991, user pi
> random seed for tests: 1518709083
> guix build: package 'superseded' has been superseded by 'bar'
> ++ guix build bar -d
> accepted connection from pid 23282, user pi
> random seed for tests: 1518709358
> + test /home/pi/code/guix/test-tmp/store/y6l76g4i1m2q0ckliw4941x4sa0wa24w-bar-9001.drv = ''
> + rm -rf t-guix-build-10577
> FAIL tests/guix-build.sh (exit status: 1)

This one looks fishy, I don’t see how it could happen (see
tests/guix-build.sh). Is it reproducible?

You can run “make check TESTS=tests/guix-build.sh” to run just this
test.

Toggle quote (14 lines)
> In guix/scripts/package.scm:
> 250:34 5 (_ #<package ifdtool@4.7 gnu/packages/flashing-tools.s?> ?)
> In srfi/srfi-1.scm:
> 466:18 4 (fold #<procedure 1c4a100 at guix/ui.scm:1158:8 (metri?> ?)
> In guix/ui.scm:
> 1161:13 3 (_ _ 0)
> 1040:23 2 (texi->plain-text _)
> In texinfo.scm:
> 1131:22 1 (parse _)
> 966:36 0 (loop #<input: string 1c20038> (*fragment*) #<procedur?> ?)
>
> texinfo.scm:966:36: In procedure loop:
> texinfo.scm:966:36: Throw to key `parser-error' with args `(#f "Unknown command" ifdtool)'.

This one was fixed in commit ec0f3d0a5bdc1f56308aeff5dabfbb3ab18b9810.

Thanks,
Ludo’.
M
M
Martin Castillo wrote on 16 Feb 2018 14:58
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 30476@debbugs.gnu.org)
9613f64e-f753-0de3-aea1-e4be0400a459@uni-bremen.de
On 16.02.2018 14:00, Ludovic Courtès wrote:
Toggle quote (20 lines)
> Martin Castillo <castilma@uni-bremen.de> skribis:
>
>> ++ guix build superseded -d
>> accepted connection from pid 22991, user pi
>> random seed for tests: 1518709083
>> guix build: package 'superseded' has been superseded by 'bar'
>> ++ guix build bar -d
>> accepted connection from pid 23282, user pi
>> random seed for tests: 1518709358
>> + test /home/pi/code/guix/test-tmp/store/y6l76g4i1m2q0ckliw4941x4sa0wa24w-bar-9001.drv = ''
>> + rm -rf t-guix-build-10577
>> FAIL tests/guix-build.sh (exit status: 1)
>
> This one looks fishy, I don’t see how it could happen (see
> tests/guix-build.sh). Is it reproducible?
>
> You can run “make check TESTS=tests/guix-build.sh” to run just this
> test.
>

No, it is not reproducible.

Toggle quote (17 lines)
>> In guix/scripts/package.scm:
>> 250:34 5 (_ #<package ifdtool@4.7 gnu/packages/flashing-tools.s?> ?)
>> In srfi/srfi-1.scm:
>> 466:18 4 (fold #<procedure 1c4a100 at guix/ui.scm:1158:8 (metri?> ?)
>> In guix/ui.scm:
>> 1161:13 3 (_ _ 0)
>> 1040:23 2 (texi->plain-text _)
>> In texinfo.scm:
>> 1131:22 1 (parse _)
>> 966:36 0 (loop #<input: string 1c20038> (*fragment*) #<procedur?> ?)
>>
>> texinfo.scm:966:36: In procedure loop:
>> texinfo.scm:966:36: Throw to key `parser-error' with args `(#f "Unknown command" ifdtool)'.
>
> This one was fixed in commit ec0f3d0a5bdc1f56308aeff5dabfbb3ab18b9810.
>

May I ask, how these kind of errors slip in? Does the reviewer only look
at the technical parts of patches?

Thanks
Martin
L
L
Ludovic Courtès wrote on 16 Feb 2018 16:16
(name . Martin Castillo)(address . castilma@uni-bremen.de)(address . 30476-done@debbugs.gnu.org)
87wozdm0co.fsf@gnu.org
Martin Castillo <castilma@uni-bremen.de> skribis:

Toggle quote (23 lines)
> On 16.02.2018 14:00, Ludovic Courtès wrote:
>> Martin Castillo <castilma@uni-bremen.de> skribis:
>>
>>> ++ guix build superseded -d
>>> accepted connection from pid 22991, user pi
>>> random seed for tests: 1518709083
>>> guix build: package 'superseded' has been superseded by 'bar'
>>> ++ guix build bar -d
>>> accepted connection from pid 23282, user pi
>>> random seed for tests: 1518709358
>>> + test /home/pi/code/guix/test-tmp/store/y6l76g4i1m2q0ckliw4941x4sa0wa24w-bar-9001.drv = ''
>>> + rm -rf t-guix-build-10577
>>> FAIL tests/guix-build.sh (exit status: 1)
>>
>> This one looks fishy, I don’t see how it could happen (see
>> tests/guix-build.sh). Is it reproducible?
>>
>> You can run “make check TESTS=tests/guix-build.sh” to run just this
>> test.
>>
>
> No, it is not reproducible.

OK, I’ll close the bug but do reopen it if it shows up again.

Toggle quote (20 lines)
>>> In guix/scripts/package.scm:
>>> 250:34 5 (_ #<package ifdtool@4.7 gnu/packages/flashing-tools.s?> ?)
>>> In srfi/srfi-1.scm:
>>> 466:18 4 (fold #<procedure 1c4a100 at guix/ui.scm:1158:8 (metri?> ?)
>>> In guix/ui.scm:
>>> 1161:13 3 (_ _ 0)
>>> 1040:23 2 (texi->plain-text _)
>>> In texinfo.scm:
>>> 1131:22 1 (parse _)
>>> 966:36 0 (loop #<input: string 1c20038> (*fragment*) #<procedur?> ?)
>>>
>>> texinfo.scm:966:36: In procedure loop:
>>> texinfo.scm:966:36: Throw to key `parser-error' with args `(#f "Unknown command" ifdtool)'.
>>
>> This one was fixed in commit ec0f3d0a5bdc1f56308aeff5dabfbb3ab18b9810.
>>
>
> May I ask, how these kind of errors slip in? Does the reviewer only look
> at the technical parts of patches?

Reviewers and contributors do their best I believe, but sometimes errors
slip through. It’s rare though.

This particular issue would have been caught by ‘guix lint’.

Ludo’.
Closed
?