unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Castillo <castilma@uni-bremen.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30476@debbugs.gnu.org
Subject: bug#30476: failing test-suite
Date: Fri, 16 Feb 2018 14:58:39 +0100	[thread overview]
Message-ID: <9613f64e-f753-0de3-aea1-e4be0400a459@uni-bremen.de> (raw)
In-Reply-To: <878tbtozrv.fsf@gnu.org>



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.

>> 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

  reply	other threads:[~2018-02-16 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16  0:02 bug#30476: failing test-suite Martin Castillo
2018-02-16  9:39 ` Ludovic Courtès
2018-02-16 11:51   ` Martin Castillo
2018-02-16 13:00     ` Ludovic Courtès
2018-02-16 13:58       ` Martin Castillo [this message]
2018-02-16 15:16         ` Ludovic Courtès

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=9613f64e-f753-0de3-aea1-e4be0400a459@uni-bremen.de \
    --to=castilma@uni-bremen.de \
    --cc=30476@debbugs.gnu.org \
    --cc=ludo@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).