After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778600 - cve-2015-4491 test fails on Ubuntu
cve-2015-4491 test fails on Ubuntu
Status: RESOLVED DUPLICATE of bug 765094
Product: gdk-pixbuf
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gdk-pixbuf-maint
gdk-pixbuf-maint
Depends on:
Blocks:
 
 
Reported: 2017-02-14 10:36 UTC by Jeremy Bicha
Modified: 2017-07-26 14:49 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build log (314.98 KB, text/plain)
2017-02-14 10:36 UTC, Jeremy Bicha 		Details

Description Jeremy Bicha 2017-02-14 10:36:43 UTC 
Created attachment 345720 [details]
build log

The cve-2015-4491 test fails on amd64 on Ubuntu's builders.

I was able to build gdk-pixbuf 2.36.5 in a Launchpad PPA successfully, but it failed to build with 5 attempts so far a few hours later in Ubuntu directly.

On arm64, it failed the first time at the same test but it passed the second time.

By the way, the reason I tried it in the PPA because my computer locked up during the tests (though not at this point yet) twice.

I found this bug in a quick search: https://bugzilla.gnome.org/753908

Log excerpt:

ERROR: cve-2015-4491
====================

Killed
# random seed: R02S3b117058dca8dfb302c94b0b565c6574
1..4
# Start of pixbuf tests
# Start of cve-2015-4491 tests
ERROR: cve-2015-4491 - too few tests run (expected 4, got 0)
ERROR: cve-2015-4491 - exited with status 137 (terminated by signal 9?)
Comment 1 Philip Withnall 2017-03-21 10:11:18 UTC 
Can you possibly get a gdb trace from the tests failing? I haven’t ever seen this when running the tests locally.

How much memory is available on those build machines?
Comment 2 Bastien Nocera 2017-07-26 14:44:45 UTC 
FWIW, it will now allocate 1509949441 * 4 bytes, so about 5760 megs of RAM and free them straight away.
Comment 3 Bastien Nocera 2017-07-26 14:49:17 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 765094 ***