ffmpeg-4.2.2 fails to build on native i686-linux

  • Open
  • quality assurance status badge
Details
5 participants
  • Jan Nieuwenhuizen
  • Ludovic Courtès
  • Maxim Cournoyer
  • ndre
  • zimoun
Owner
unassigned
Submitted by
Jan Nieuwenhuizen
Severity
normal
J
J
Jan Nieuwenhuizen wrote on 22 Feb 2020 16:47
(address . bug-guix@gnu.org)
871rqm7hfh.fsf@gnu.org
Hi,

When building ffmpeg-4.2.2 (current master, 8d1b22b27fba3d1e4310f02a5897d231b42ca117)
natively on 32bit hardware, the build fails because of two failing tests
(full log attached)

Toggle snippet (20 lines)
--- ./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
Test filter-pixdesc-grayf32be failed. Look at tests/data/fate/filter-pixdesc-grayf32be.err for details.
make: *** [tests/Makefile:238: fate-filter-pixdesc-grayf32be] Error 1
make: *** Waiting for unfinished jobs....
Test filter-pixdesc-grayf32le failed. Look at tests/data/fate/filter-pixdesc-grayf32le.err for details.
make: *** [tests/Makefile:238: fate-filter-pixdesc-grayf32le] Error 1

Test suite failed, dumping logs.
command "make" "fate" "-j" "2" failed with status 2

How to attempt fixing this?

Building it on 64 bit hardware (much faster!) works for me, i.e. this

guix build --system=i686-linux ffmpeg

works for me and can be used as a substitute...

Together with qemu-minimal-2.10 depending on ffmpeg
(https://bugs.gnu.org/39737)and no available substitutes this made for
a pretty rough "guix system reconfigure"-experience today.

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?

Apart from this hiccup I had a smooth upgrade from guix 0.14,
impressive!

Greetings,
janneke
Attachment: lbnqlz4ppj0bgckksn7r25p385qawy-ffmpeg-4.2.2.drv.bz2
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com| Avatar® http://AvatarAcademy.com
N
N
ndre wrote on 6 Mar 2020 13:04
(address . 39738@debbugs.gnu.org)
20200306120442.GA7207@andel
I'm also hitting this bug, though the failing tests are
different. Here, audiodsp fails. Current commit is
aac148a87b9a79b9992b8b1a9d76c217175d4a88.

Test checkasm-audiodsp failed. Look at tests/data/fate/checkasm-audiodsp.err for details.
make: *** [tests/Makefile:237: fate-checkasm-audiodsp] Error 1
make: *** Waiting for unfinished jobs....
TEST checkasm-bswapdsp

Test suite failed, dumping logs.
command "make" "fate" "-j" "2" failed with status 2

----------------------------------------------------

tests/data/fate/checkasm-audiodsp.err:

checkasm: using random seed 854121083
MMX:
- audiodsp.audiodsp [OK]
MMXEXT:
- audiodsp.audiodsp [OK]
SSE:
- audiodsp.audiodsp [OK]
SSE2:
- audiodsp.audiodsp [OK]
SSSE3:
audiodsp.vector_clip_int32_ssse3 (audiodsp.c:111)
- audiodsp.audiodsp [FAILED]
checkasm: 1 of 6 tests have failed

---------------------------------------------------

Full log attached.
Attachment: nihy0hya21wm4dpqv7iq2z8q80qq92-ffmpeg-4.2.2.drv.bz2
-----BEGIN PGP SIGNATURE-----

iQI5BAABCgAjFiEEIBdLYNLH+F+MBdSrYrJ+WmBEwoIFAl5iPFUFgwPCZwAACgkQ
YrJ+WmBEwoKk5w//ZMVxH5R+6qCkVbmTYitcbEGWo/4p0jAQgCCNDS+R7l+mQzSa
9Ky2d89OzAZQkq5Yy+67gXPXq0nNSd3vmFYADCbxZRviVYMgiCN1Nf465CC3mHBC
OLQcubxPscWKk9KdOMM/b7CLAuwbZW8F9ud20bavdRsy8QU34SqTvJJQAYGgnoDZ
jyOb39UcDO/MBlRNmisjjrkYu8KhNOAHfs276s0Oa7TKfWypIMxp1nJEb+pXH/Zc
tJMhtRbNRJJTZjNCXpxuyl9nv83kEMZ3apnyNtNO/8jZexOLmHZB5ZAI3rhiA5Fi
J6BYY2snARAsaggvxorbp+RSukqsDqfDR4kACZOac6eJhLt8G8W1vibXPs6bwpTi
lUtd1gAGLei+/erPQWb5aKiEroEts9ct8+rtwT9sF+aWWb2aYS5XQ7TjQOpsMYlm
FxjZX4rNvF1Lq72NdsjvdrzGNw7aizcxr9Y0hKJnZtOlXbZ2OCp3oMW0ls6/rdOv
rL90BHQETWk01S1g62wrZcU3mC3G4li3fhzLIrPPPFR5M+PNgDptT7pdME8qz5fB
FWllFkcXQ55B0eVoi4VakVi7G5g43puwr9eWw46rWxf/n06zkHWldue8lVc3bJl1
p/9HXVYdr9vvyvSuop3Dw5PPLk05yUb1bklkN9DowqwZzsldFBzrc+hCMY8=
=yJa9
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 8 Mar 2020 21:49
Re: bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux
(name . Jan Nieuwenhuizen)(address . janneke@gnu.org)(address . 39738@debbugs.gnu.org)
87sgii8tdp.fsf@gnu.org
Hi,

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

Toggle quote (15 lines)
> 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. :-/

Toggle quote (4 lines)
> 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. :-)

Toggle quote (3 lines)
> Apart from this hiccup I had a smooth upgrade from guix 0.14,
> impressive!

From 0.14, woow.

Ludo’.
M
M
Maxim Cournoyer wrote on 8 Aug 2021 05:53
(name . Jan Nieuwenhuizen)(address . janneke@gnu.org)(address . 39738@debbugs.gnu.org)
87tuk0384c.fsf@gmail.com
Hi,

Jan Nieuwenhuizen <janneke@gnu.org> writes:

Toggle quote (33 lines)
> Hi,
>
> 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
> Test filter-pixdesc-grayf32be failed. Look at tests/data/fate/filter-pixdesc-grayf32be.err for details.
> make: *** [tests/Makefile:238: fate-filter-pixdesc-grayf32be] Error 1
> make: *** Waiting for unfinished jobs....
> Test filter-pixdesc-grayf32le failed. Look at tests/data/fate/filter-pixdesc-grayf32le.err for details.
> make: *** [tests/Makefile:238: fate-filter-pixdesc-grayf32le] Error 1
>
> Test suite failed, dumping logs.
> command "make" "fate" "-j" "2" failed with status 2
>
> How to attempt fixing this?
>
> Building it on 64 bit hardware (much faster!) works for me, i.e. this
>
> guix build --system=i686-linux ffmpeg
>
> works for me and can be used as a substitute...

I don't have real 32 bits hardware to test on, but could you please test
ffmpeg 4.4 on such hardware if you have a chance and see if the issues
still exist?

Thanks,

Maxim
Z
Z
zimoun wrote on 18 Oct 2022 17:50
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
867d0xyvu9.fsf@gmail.com
Hi,

It is about the old bug#39738 [1].


On Sat, 07 Aug 2021 at 23:53, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

Toggle quote (10 lines)
>> Building it on 64 bit hardware (much faster!) works for me, i.e. this
>>
>> guix build --system=i686-linux ffmpeg
>>
>> works for me and can be used as a substitute...
>
> I don't have real 32 bits hardware to test on, but could you please test
> ffmpeg 4.4 on such hardware if you have a chance and see if the issues
> still exist?

Friendly ping. :-)

Is ffmpeg still an issue an real 32 bits hardware?

Cheers,
simon
S
S
Simon Tournier wrote on 17 Oct 2023 00:31
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
86zg0ip5bs.fsf@gmail.com
Hi,

It is about the old bug#39738 [1].



On Tue, 18 Oct 2022 at 17:50, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (16 lines)
> On Sat, 07 Aug 2021 at 23:53, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>>> Building it on 64 bit hardware (much faster!) works for me, i.e. this
>>>
>>> guix build --system=i686-linux ffmpeg
>>>
>>> works for me and can be used as a substitute...
>>
>> I don't have real 32 bits hardware to test on, but could you please test
>> ffmpeg 4.4 on such hardware if you have a chance and see if the issues
>> still exist?
>
> Friendly ping. :-)
>
> Is ffmpeg still an issue an real 32 bits hardware?

I do not have real 32 bits hardware to test on, but

guix build --system=i686-linux ffmpeg

works for me with Guix 6113e05. It outputs:

/gnu/store/wprpm76xy3b0312579dgv0akzy6k9llh-ffmpeg-6.0-debug
/gnu/store/y2mvpk6bna381ldskfmh6rzy1j34xnms-ffmpeg-6.0

Moreover, CI reports the failures for:


and passes for:


Therefore, I am in favor to close it.

WDYT?

Cheers,
simon
M
M
Maxim Cournoyer wrote on 17 Oct 2023 16:31
(name . Simon Tournier)(address . zimon.toutoune@gmail.com)
87mswhuxq2.fsf@gmail.com
Hi Simon,

Simon Tournier <zimon.toutoune@gmail.com> writes:

[...]

Toggle quote (27 lines)
>> Is ffmpeg still an issue an real 32 bits hardware?
>
> I do not have real 32 bits hardware to test on, but
>
> guix build --system=i686-linux ffmpeg
>
> works for me with Guix 6113e05. It outputs:
>
> /gnu/store/wprpm76xy3b0312579dgv0akzy6k9llh-ffmpeg-6.0-debug
> /gnu/store/y2mvpk6bna381ldskfmh6rzy1j34xnms-ffmpeg-6.0
>
> Moreover, CI reports the failures for:
>
> v3.4.11 https://ci.guix.gnu.org/build/1836841/details
>
> and passes for:
>
> v2.1.3 https://ci.guix.gnu.org/build/2041193/details
> v2.8.20 https://ci.guix.gnu.org/build/1836825/details
> v4.4.2 https://ci.guix.gnu.org/build/1836824/details
> v5.1.3 https://ci.guix.gnu.org/build/1836833/details
> v6.0 https://ci.guix.gnu.org/build/1836842/details
>
> Therefore, I am in favor to close it.
>
> WDYT?

Sounds reasonable, thanks for the verifications!

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 39738@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 39738
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch