Hi, Jan Nieuwenhuizen <jann...@gnu.org> skribis:
> 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. :-/ > 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. :-) > Apart from this hiccup I had a smooth upgrade from guix 0.14, > impressive! >From 0.14, woow. Ludo’.