Bug#954196: gegl: FTBFS on mipsel: tests/compositions/reference/rgbe-save.hdr and .../output/rgbe-save.hdr differ

[Simon McVittie]

Source: gegl
Version: 0.4.22-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 951821 by -1

https://buildd.debian.org/status/fetch.php?pkg=gegl&arch=mipsel&ver=0.4.22-2&stamp=1584490046&raw=0
> [swscaler @ 0x5617e750] No accelerated colorspace conversion found from yuv420p to rgb24.
> missing reference, assuming SUCCESS
> PASS color-reduction.xml
> missing reference, assuming SUCCESS
> PASS jpg-load-datauri.xml
> missing reference, assuming SUCCESS
> PASS pnm-ascii-load.xml
> missing reference, assuming SUCCESS
> PASS pnm-raw-load.xml
> missing reference, assuming SUCCESS
> PASS rgbe-load.xml
> 
> (gegl-imgcmp:1189): GEGL-WARNING **: 00:03:06.812: max diff is not a valid property of gegl:image-compare 0x55776830
> /<<PKGBUILDDIR>>/tests/compositions/reference/rgbe-save.hdr and /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/tests/compositions/output/rgbe-save.hdr differ
>   wrong pixels   : 165/12288 (1.34%)
>   max ?e         : 67326627421669684888669005176245981626127818201330704240878079155477023449696839256119546828890322554026762884581407459611684012658109431614078423083822172532225793664776343589445197580928856114285850164049130170201566309394530763936055595205809030148151018621390290944.000
>   avg ?e (wrong) : 67326627421669684888669005176245981626127818201330704240878079155477023449696839256119546828890322554026762884581407459611684012658109431614078423083822172532225793664776343589445197580928856114285850164049130170201566309394530763936055595205809030148151018621390290944.000(wrong) 57895085948248197003310861778540597530344540911046658743056637836873978536706733178284242874418852779814501765638059266549873720618904958362702683089689120708187862881929758991439906547451878104338721332513031507467342755888365810233077968491152966828328813401751945216.000(total)
> FAIL rgbe-save.xml
> missing reference, assuming SUCCESS
> PASS shift.xml
> missing reference, assuming SUCCESS
> PASS stretch-contrast-hsv.xml
> missing reference, assuming SUCCESS
> PASS tiff-load.xml
> missing reference, assuming SUCCESS
> PASS tile.xml
> === Test Results ===
>  tests passed:  9
>  tests skipped: 0
>  tests failed:  1
> ======  FAIL  ======

We can't get the binary output from a failing build on a buildd, so it's
impossible to say whether this is serious or not unless it can be
reproduced on a porterbox or similar (which I'm trying to do now).

    smcv