From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 31868-done@debbugs.gnu.org
Subject: bug#31868: Test failure for GnuCash 3.3 (previously 3.0)
Date: Wed, 02 Jan 2019 17:33:04 -0500 [thread overview]
Message-ID: <87pntepu5b.fsf@apteryx.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <8736qbfpkp.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 02 Jan 2019 09:09:42 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> Efraim Flashner <efraim@flashner.co.il> writes:
>
>> On Tue, Jan 01, 2019 at 03:15:09PM -0500, Maxim Cournoyer wrote:
>>> Using latest Guix, GnuCash 3.3 fails its test suite by only one test:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> [fail] line:644, test: dual amount column, first transaction correct
>>> transaction.scm/display options
>>> -> expected: ("01/03/18" "$103 income" "Root.Asset.Bank" "$103.00" "$103.00")
>>> -> obtained: ("01/03/19" "$103 income" "Root.Asset.Bank" "$103.00" "$103.00")
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>
>> Haven't looked at the test yet, is this a 'yyyy' vs 'YYYY' error in ISO8601?
>
> To me this looks like the test assumes that we’re running it in 2018,
> not $current_year.
Good flair; it turned out to be exactly this.
Fixed with commit 707efe171a4e0e542a7d969c130195fa94b5d615. Closing.
Thank you,
Maxim
prev parent reply other threads:[~2019-01-02 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 1:47 bug#31868: Tests failures for GnuCash 3.0 Maxim Cournoyer
2019-01-01 20:15 ` bug#31868: Test failure for GnuCash 3.3 (previously 3.0) Maxim Cournoyer
2019-01-02 7:45 ` Efraim Flashner
2019-01-02 8:09 ` Ricardo Wurmus
2019-01-02 22:33 ` Maxim Cournoyer [this message]
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=87pntepu5b.fsf@apteryx.i-did-not-set--mail-host-address--so-tickle-me \
--to=maxim.cournoyer@gmail.com \
--cc=31868-done@debbugs.gnu.org \
--cc=rekado@elephly.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 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).