[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#879076: marked as done (libopenshot: FTBFS on ppc64(el) and powerpc: several tests report discrepancies)

Your message dated Sun, 23 Mar 2025 16:09:44 +0100
with message-id <441c9eb3-ba00-41d2-9fc1-1d59ea53d195@debian.org>
and subject line Re: libopenshot: FTBFS on ppc64(el) and powerpc: several tests report discrepancies
has caused the Debian Bug report #879076,
regarding libopenshot: FTBFS on ppc64(el) and powerpc: several tests report discrepancies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
879076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879076
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libopenshot
Version: 0.1.8+ds1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-powerpc@lists.debian.org

Builds of libopenshot for ppc64el and the non-release architectures
powerpc and ppc64 have been failing with mostly identical errors, as
detailed at

https://buildd.debian.org/status/fetch.php?pkg=libopenshot&arch=ppc64el&ver=0.1.8%2Bds1-1&stamp=1508343041&raw=0
https://buildd.debian.org/status/fetch.php?pkg=libopenshot&arch=powerpc&ver=0.1.8%2Bds1-1&stamp=1508342906&raw=0
https://buildd.debian.org/status/fetch.php?pkg=libopenshot&arch=ppc64&ver=0.1.8%2Bds1-1&stamp=1508342970&raw=0

The only difference in errors between the architectures is that on
ppc64, FFmpegReader_Check_Video_File crashes (at line 82) before it
can report any errors, as does FFmpegWriter_Test_Webm (which is
otherwise successful).

Apart from that, there are a total of 29 discrepancies across the
tests Clip_Effects, FFmpegReader_Check_Video_File,
ImageWriter_Test_Gif, and Timeline_Check_Two_Track_Video.

In Clip_Effects, three values that should be 255 come out 239, and
three that should be 0 come out 16.  (NB: 16 + 239 = 255.)

In FFmpegReader_Check_Video_File (when it doesn't crash altogether),
five values come out somewhat greater than expected.

In ImageWriter_Test_Gif and Timeline_Check_Two_Track_Video, a number
of values come out 0 -- four in ImageWriter_Test_Gif and fourteen in
Timeline_Check_Two_Track_Video.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu

--- End Message ---
--- Begin Message --- 
Version: 0.2.7+dfsg1-1

This is at least true for ppc64el

--- End Message ---
Reply to: