From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 32008@debbugs.gnu.org
Subject: [bug#32008] [PATCH] gnu: ledger: Skip failing test.
Date: Tue, 03 Jul 2018 21:22:46 +0200 [thread overview]
Message-ID: <87r2kkgm49.fsf@gnu.org> (raw)
In-Reply-To: <cu71sckvgsh.fsf@systemreboot.net> (Arun Isaac's message of "Tue, 03 Jul 2018 14:26:30 +0530")
Arun Isaac <arunisaac@systemreboot.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> It would be nice to make separate patches for unrelated things (for
>> instance invoke and phase returns have nothing to do with skipping the
>> test), but otherwise LGTM.
>
> I bunched these together because the invoke change and home-page change
> were fairly minor things. But, if you insist, I'll push these as three
> separate commits (one for skipping the test, one for invoke/phase
> returns, and one for the home-page change).
Honestly it doesn’t matter much here, but what I like about
one-patch-for-one-thing is that it makes review and bug hunting (when
you later run ‘git annotate’ to understand what happened) easier.
>>> + ;; Skip failing tests during the check phase.
>>> + #:make-flags (list "ARGS=-E BaselineTest_cmd-org")
>>
>> Do you have more info about the test or an upstream bug report?
>
> Yes, this is a known upstream bug. It exists even in the latest git
> checkout.
>
> https://github.com/ledger/ledger/issues/550
>
> I also posted to this bug report mentioning our problem in GuixSD. I
> will leave the URI to this bug report in the comments before
> #:make-flags.
Perfect.
> Shall I push with the above mentioned changes?
Sure!
Thank you,
Ludo’.
next prev parent reply other threads:[~2018-07-03 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 17:07 [bug#32008] [PATCH] gnu: ledger: Skip failing test Arun Isaac
2018-07-02 15:38 ` Ludovic Courtès
[not found] ` <cu71sckvgsh.fsf@systemreboot.net>
2018-07-03 19:22 ` Ludovic Courtès [this message]
2018-07-04 12:54 ` bug#32008: " Arun Isaac
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=87r2kkgm49.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32008@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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.