Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout
Control: tags -1 pending Hi, On 08/04/18 11:18, Niels Thykier wrote: > On Sat, 7 Apr 2018 21:38:53 +0100 James Cowgill wrote: >> Source: ffmpeg >> Version: 7:3.4.1-1 >> Severity: serious >> Tags: sid buster >> >> For some reason ffmpeg has started FTBFS with this error: >>> TESTvsynth2-zlib >>> /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" >>> "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt >>> yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 >>> -pix_fmt yuv420p -vsync 0 " -keep ""' '' >>> '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' >>> '' '' '' >>> /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f >>> rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags >>> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none >>> -threads 1 -thread_type frame+slice -i >>> /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct >>> simple -dct fastint -c zlib -flags +bitexact -sws_flags >>> +accurate_rnd+bitexact -fflags +bitexact -f avi -y >>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi >>> /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all >>> -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact >>> -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i >>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads >>> 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags >>> +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo >>> -y >>> /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo >>> make[2]: Leaving directory '/<>/debian/standard' >>> make[2]: write error: stdout >>> dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code >>> 1 >>> make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25 >>> make[1]: Leaving directory '/<>' >>> make: *** [debian/rules:192: binary] Error 2 >>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit >>> status 2 >> >> This can be seen on the reproducible builds first seen 2018-03-15 >> affecting 3.4 and 3.5 in experimental. >> >> I'm guessing this has something to do with "make -O" which was enabled >> recently in debhelper, but I haven't checked. >> >> James > > Hi James, > > In a recent upload, debhelper started using -Oline instead of -O. Does > that solve this problem for you? (It was done unrelated to this bug, > but looking at the documentation for -O, I suspect it might help here as > well) As me and Adrian said on IRC, it does not. The problem was nodejs leaving stderr in non-blocking mode and I've committed this to fix it. So no bugs in debhelper here. https://salsa.debian.org/multimedia-team/ffmpeg/commit/71b483f31e5a411a02717278e0a30323965c2c88 Thanks, James signature.asc Description: OpenPGP digital signature
Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout
On Sat, 7 Apr 2018 21:38:53 +0100 James Cowgill wrote: > Source: ffmpeg > Version: 7:3.4.1-1 > Severity: serious > Tags: sid buster > > For some reason ffmpeg has started FTBFS with this error: > > TESTvsynth2-zlib > > /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" > > "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt > > yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 > > -pix_fmt yuv420p -vsync 0 " -keep ""' '' > > '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' > > '' '' '' > > /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f > > rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags > > +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none > > -threads 1 -thread_type frame+slice -i > > /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct > > simple -dct fastint -c zlib -flags +bitexact -sws_flags > > +accurate_rnd+bitexact -fflags +bitexact -f avi -y > > /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi > > /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all > > -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact > > -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i > > /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads > > 1 -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags > > +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo > > -y > > /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo > > make[2]: Leaving directory '/<>/debian/standard' > > make[2]: write error: stdout > > dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code > > 1 > > make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25 > > make[1]: Leaving directory '/<>' > > make: *** [debian/rules:192: binary] Error 2 > > dpkg-buildpackage: error: debian/rules binary subprocess returned exit > > status 2 > > This can be seen on the reproducible builds first seen 2018-03-15 > affecting 3.4 and 3.5 in experimental. > > I'm guessing this has something to do with "make -O" which was enabled > recently in debhelper, but I haven't checked. > > James > Hi James, In a recent upload, debhelper started using -Oline instead of -O. Does that solve this problem for you? (It was done unrelated to this bug, but looking at the documentation for -O, I suspect it might help here as well) Thanks, ~Niels
Bug#895154: ffmpeg: FTBFS - make[2]: write error: stdout
Source: ffmpeg Version: 7:3.4.1-1 Severity: serious Tags: sid buster For some reason ffmpeg has started FTBFS with this error: > TESTvsynth2-zlib > /<>/tests/fate-run.sh fate-vsynth2-zlib "" "" > "/<>/debian/standard" 'enc_dec "rawvideo -s 352x288 -pix_fmt > yuv420p " tests/data/vsynth2.yuv avi "-c zlib " rawvideo "-s 352x288 -pix_fmt > yuv420p -vsync 0 " -keep ""' '' > '/<>/tests/ref/vsynth/vsynth2-zlib' '' '1' '' '' '' '' '' '1' '' > '' '' > /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all -f > rawvideo -s 352x288 -pix_fmt yuv420p -threads 1 -idct simple -flags +bitexact > -sws_flags +accurate_rnd+bitexact -fflags +bitexact -hwaccel none -threads 1 > -thread_type frame+slice -i > /<>/debian/standard/tests/data/vsynth2.yuv -threads 1 -idct > simple -dct fastint -c zlib -flags +bitexact -sws_flags > +accurate_rnd+bitexact -fflags +bitexact -f avi -y > /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi > /<>/debian/standard/ffmpeg -nostdin -nostats -cpuflags all > -threads 1 -idct simple -flags +bitexact -sws_flags +accurate_rnd+bitexact > -fflags +bitexact -hwaccel none -threads 1 -thread_type frame+slice -i > /<>/debian/standard/tests/data/fate/vsynth2-zlib.avi -threads 1 > -idct simple -dct fastint -s 352x288 -pix_fmt yuv420p -vsync 0 -flags > +bitexact -sws_flags +accurate_rnd+bitexact -fflags +bitexact -f rawvideo -y > /<>/debian/standard/tests/data/fate/vsynth2-zlib.out.rawvideo > make[2]: Leaving directory '/<>/debian/standard' > make[2]: write error: stdout > dh_auto_test: cd debian/standard && make -j4 -O check -k returned exit code 1 > make[1]: *** [debian/rules:231: override_dh_auto_test-arch] Error 25 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:192: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 This can be seen on the reproducible builds first seen 2018-03-15 affecting 3.4 and 3.5 in experimental. I'm guessing this has something to do with "make -O" which was enabled recently in debhelper, but I haven't checked. James signature.asc Description: OpenPGP digital signature
