unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: 43832@debbugs.gnu.org
Subject: bug#43832: beets build fails in tests
Date: Tue, 06 Oct 2020 18:41:36 +0200	[thread overview]
Message-ID: <87o8lf71dr.fsf@rohleder.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]


commit 4913e8ede09bf6f4efc27d3fb6e224cb87bbb9ee (python-mutagen update)
breaks a test in beets:

...
======================================================================
FAIL: test_read_audio_properties (test.test_mediafile.AIFFTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/guix-build-beets-1.4.9.drv-0/beets-1.4.9/test/test_mediafile.py", line 440, in test_read_audio_properties
    self.assertEqual(getattr(mediafile, key), value)
AssertionError: 16 != 0

======================================================================
FAIL: test_read_audio_properties (test.test_mediafile.WavpackTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/guix-build-beets-1.4.9.drv-0/beets-1.4.9/test/test_mediafile.py", line 440, in test_read_audio_properties
    self.assertEqual(getattr(mediafile, key), value)
AssertionError: 16 != 0

----------------------------------------------------------------------
Ran 1901 tests in 124.212s


guix time-machine --commit=bd994bbb2003f3af936836bbf148660a81a3037b -- build beets
works.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

             reply	other threads:[~2020-10-06 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 16:41 Michael Rohleder [this message]
2020-10-11 10:20 ` bug#43832: beets build fails in tests Michael Rohleder

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=87o8lf71dr.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=43832@debbugs.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).