From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 39738@debbugs.gnu.org
Subject: bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux
Date: Sun, 08 Mar 2020 21:49:06 +0100 [thread overview]
Message-ID: <87sgii8tdp.fsf@gnu.org> (raw)
In-Reply-To: <871rqm7hfh.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Sat, 22 Feb 2020 16:47:14 +0100")
Hi,
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> When building ffmpeg-4.2.2 (current master, 8d1b22b27fba3d1e4310f02a5897d231b42ca117)
> natively on 32bit hardware, the build fails because of two failing tests
> (full log attached)
>
> --- ./tests/ref/fate/filter-pixdesc-grayf32be 2019-12-31 21:35:25.000000000 +0000
> +++ tests/data/fate/filter-pixdesc-grayf32be 2020-02-22 15:15:50.209912771 +0000
> @@ -1 +1 @@
> -pixdesc-grayf32be 9b23c74e8e8ffae5d7c7e82bbf5929da
> +pixdesc-grayf32be 01816b882016239d0cf84241818926a4
> --- ./tests/ref/fate/filter-pixdesc-grayf32le 2019-12-31 21:35:25.000000000 +0000
> +++ tests/data/fate/filter-pixdesc-grayf32le 2020-02-22 15:15:50.253914049 +0000
> @@ -1 +1 @@
> -pixdesc-grayf32le 291f074a24c44799a1f437d1c55556f1
> +pixdesc-grayf32le 1b234318d06d5a76e980c376ad8764e5
Bah, it’s an all-too-common kind of failure. :-/
> I worked around this by adding a ffmpeg package that ignored the check
> phase (#:tests? #f); I am wondering if we could we enable (something
> like) that from the command line? WDYT?
We could add a package transformation option that adds #:tests? #f.
WDYT?
Though it’d be nice to not have test failures in the first place. :-)
> Apart from this hiccup I had a smooth upgrade from guix 0.14,
> impressive!
From 0.14, woow.
Ludo’.
next prev parent reply other threads:[~2020-03-08 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 15:47 bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux Jan Nieuwenhuizen
2020-03-06 12:04 ` ndre
2020-03-08 20:49 ` Ludovic Courtès [this message]
2021-08-08 3:53 ` Maxim Cournoyer
2022-10-18 15:50 ` zimoun
2023-10-16 22:31 ` Simon Tournier
2023-10-17 14:31 ` Maxim Cournoyer
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=87sgii8tdp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39738@debbugs.gnu.org \
--cc=janneke@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).