all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "André Batista" <nandre@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: dariqq@posteo.net, 72917@debbugs.gnu.org
Subject: bug#72917: ffmpeg@{3,4,5} build failures on i686-linux
Date: Thu, 5 Sep 2024 20:47:39 -0300	[thread overview]
Message-ID: <ZtpDG7e_KsKno6II@andel> (raw)
In-Reply-To: <87plpia7f3.fsf_-_@gnu.org>

Hi,

qui 05 set 2024 às 09:25:36 (1725539136), ludo@gnu.org enviou:
> Hello,
> 
> As it turns out, while all 3 variants built fine for i686 on a machine
> of mine, there are test failures at ci.guix:
> 
> From <https://ci.guix.gnu.org/build/5613329/details>:
> 
> --8<---------------cut here---------------start------------->8---
> --- ./tests/ref/fate/filter-lavd-scalenorm	2023-11-09 23:38:51.000000000 +0000
> +++ tests/data/fate/filter-lavd-scalenorm	2024-09-04 17:57:08.701821746 +0000
> @@ -1,15 +0,0 @@
> -#tb 0: 1/5
> -#media_type 0: video
> -#codec_id 0: rawvideo
> -#dimensions 0: 128x96
> -#sar 0: 1/1
> -0,          0,          0,        1,    18432, 0xac484db5
> -0,          1,          1,        1,    18432, 0x94734db6
> -0,          2,          2,        1,    18432, 0x3fac4db3
> -0,          3,          3,        1,    18432, 0x37a94dcd
> -0,          4,          4,        1,    18432, 0x2b3e4dbb
> -0,          5,          5,        1,    18432, 0xd23a67bf
> -0,          6,          6,        1,    18432, 0x898368e1
> -0,          7,          7,        1,    18432, 0x79466438
> -0,          8,          8,        1,    18432, 0x458c5d95
> -0,          9,          9,        1,    18432, 0x9d9a56ee
> Test filter-lavd-scalenorm failed. Look at tests/data/fate/filter-lavd-scalenorm.err for details.
> make: *** [tests/Makefile:304: fate-filter-lavd-scalenorm] Error 1
> make: *** Waiting for unfinished jobs....
> TEST    filter-refcmp-psnr-rgb
> 
> Test suite failed, dumping logs.
> error: in phase 'check': uncaught exception:
> %exception #<&invoke-error program: "make" arguments: ("fate" "-j" "24") exit-status: 2 term-signal: #f stop-signal: #f> 
> phase `check' failed after 8.7 seconds
> command "make" "fate" "-j" "24" failed with status 2
> build process 18 exited with status 256
> builder for `/gnu/store/7wsa154li4w974z2p6qnaaw97ng9m8hq-ffmpeg-5.1.4.drv' failed with exit code 1
> --8<---------------cut here---------------end--------------->8---
> 
> And from <https://ci.guix.gnu.org/build/5613330/details>:
> 
> --8<---------------cut here---------------start------------->8---
> --- ./tests/ref/lavf/fits	1970-01-01 00:00:01.000000000 +0000
> +++ tests/data/fate/lavf-fits	2024-09-04 17:57:17.900035764 +0000
> @@ -1,9 +1,9 @@
>  ed9fd697d0d782df6201f6a2db184552 *./tests/data/lavf/graylavf.fits
>  5328000 ./tests/data/lavf/graylavf.fits
> -./tests/data/lavf/graylavf.fits CRC=0xbacf446c
> +./tests/data/lavf/graylavf.fits CRC=0xeb450e41
>  48e6caf6a59e32f9a8a39979c9183a7f *./tests/data/lavf/gray16belavf.fits
>  10368000 ./tests/data/lavf/gray16belavf.fits
> -./tests/data/lavf/gray16belavf.fits CRC=0xae2b58d4
> +./tests/data/lavf/gray16belavf.fits CRC=0xcc6d0df7
>  be2f7112fd193c9a909304c81e662769 *./tests/data/lavf/gbrplavf.fits
>  15408000 ./tests/data/lavf/gbrplavf.fits
>  ./tests/data/lavf/gbrplavf.fits CRC=0x04ed3828
> TEST    filter-pixdesc-yuv422p
> TEST    filter-pixdesc-yuv444p
> Test lavf-fits failed. Look at tests/data/fate/lavf-fits.err for details.
> make: *** [tests/Makefile:226: fate-lavf-fits] Error 1
> make: *** Waiting for unfinished jobs....
> 
> Are you seeing this?  Does the Internet have something to say about
> these?

No I did not see this here, all tests passed. I've tried searching
ffmpeg bug tracker and commit logs but nothing useful came up.

Is it possible to see that 'tests/data/fate/lavf-fits.err' file on
CI somehow? I don't actually expect it to be of much help though.

I also see errors on ffmpeg-3, as Dariqq mentioned, but looking at
the build history on CI it had also appeared on
<https://ci.guix.gnu.org/build/5382581/log/raw> which was before
the core-updates merge, so it seems unrelated.




  parent reply	other threads:[~2024-09-05 23:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 15:46 bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Dariqq
2024-09-01 12:15 ` Dariqq
2024-09-03 14:44   ` André Batista
2024-09-03 14:24 ` André Batista
2024-09-03 14:30   ` bug#72917: [PATCH] gnu: ffmpeg-{5, 4, 3}: Fix build on i686 with binutils 2.41 André Batista
2024-09-04 17:10     ` Ludovic Courtès
2024-09-05  7:25     ` bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Ludovic Courtès
2024-09-05 19:43       ` Dariqq
2024-09-05 23:47       ` André Batista [this message]
2024-09-11 20:10         ` André Batista
2024-09-11 21:14           ` bug#67308: bug#72917: ffmpeg-3 build failures is duplicate of bug#67308 André Batista
2024-09-12 21:16             ` bug#67308: ffmpeg-3 build failures on i686 André Batista
2024-09-03 17:39   ` bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Dariqq

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZtpDG7e_KsKno6II@andel \
    --to=nandre@riseup.net \
    --cc=72917@debbugs.gnu.org \
    --cc=dariqq@posteo.net \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.