Opened 8 years ago
Closed 8 years ago
#9499 closed enhancement (fixed)
gdk-pixbuf-2.36.7
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | 8.1 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New point version.
Change History (3)
comment:1 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 8 years ago
I get two test failures, but I disagree about the cause. At the moment:
Two tests report ERROR due to missing test data.
What I see is
ERROR: cve-2015-4491 - too few tests run (expected 4, got 0) ERROR: cve-2015-4491 - exited with status 134 (terminated by signal 6?)
and later
ERROR: pixbuf-randomly-modified - too few tests run (expected 54, got 29) ERROR: pixbuf-randomly-modified - exited with status 139 (terminated by signal 11?)
From the log for the first of those -
# random seed: R02S1805e3349838bf91fd5d82dcf3155d02 1..4 # Start of pixbuf tests ** ERROR:cve-2015-4491.c:36:test_original: assertion failed (err == NULL): BMP image has bogus header data (gdk-pixbuf-error-quark, 0) # Start of cve-2015-4491 tests ../tap-test: line 5: 17615 Aborted $1 -k --tap # ERROR:cve-2015-4491.c:36:test_original: assertion failed (err == NULL): BMP image has bogus header data (gdk-pixbuf-error-quark, 0) ERROR: cve-2015-4491 - too few tests run (expected 4, got 0) ERROR: cve-2015-4491 - exited with status 134 (terminated by signal 6?)
which sounds like either a broken test, or _incorrect_ test data.
I'm inclined to reduce the description to 'Two tests fail with ERROR messages'.
Interestingly, the status after running the tests is 0 although Error is reported.
Note:
See TracTickets
for help on using tickets.
Works for me.