[debbugs-tracker] bug#32057: closed (Test failure for GnuCash 3.3)

[GNU bug Tracking System]

Your message dated Wed, 02 Jan 2019 17:33:04 -0500
with message-id <address@hidden>
and subject line Re: bug#31868: Test failure for GnuCash 3.3 (previously 3.0)
has caused the debbugs.gnu.org bug report #31868,
regarding Test failure for GnuCash 3.3
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
31868: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31868
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: gnucash on d88b29d6b78482cdb05ac714984f6a27195e3d37 fails its testsuite Date: Thu, 5 Jul 2018 09:46:13 +0000

gnucash with guix version d88b29d6b78482cdb05ac714984f6a27195e3d37
fails its testsuite. On the record since this version, off the record
for at least a couple of weeks.

last (relevant) part of the log appended.

gnucash_fail.log
Description: Text document

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#31868: Test failure for GnuCash 3.3 (previously 3.0)
>
>
>
>
> Date: 
>
> Wed, 02 Jan 2019 17:33:04 -0500
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
>
>
>
>
> Ricardo Wurmus <address@hidden> writes:
>
> > Efraim Flashner <address@hidden> 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
>
>
> --- End Message ---