gbrowse autopkgtest failures (due to libgd3?)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gbrowse |
New
|
Unknown
|
|||
gbrowse (Debian) |
Fix Released
|
Unknown
|
|||
gbrowse (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Regression in gbrowse tests are blocking migration for nginx:
nginx (1.20.2-2ubuntu2 to 1.22.0-1ubuntu1) in proposed for 5 days
Regressions
The failures are:
not ok 5
# Test 5 got: 'ERROR' (t/05.deferredr
# Expected: 'AVAILABLE'
ok 6
not ok 7
# Test 7 got: 'ERROR' (t/05.deferredr
# Expected: 'AVAILABLE'
ok 8
not ok 9
# Test 9 got: 'ERROR' (t/05.deferredr
# Expected: 'AVAILABLE'
ok 10
not ok 11
# Test 11 got: 'ERROR' (t/05.deferredr
# Expected: 'AVAILABLE'
ok 12
not ok 13
# Test 13 got: 'ERROR' (t/05.deferredr
# Expected: 'AVAILABLE'
not ok 14
# Test 14 got: 'ERROR ERROR ERROR ERROR ERROR' (t/05.deferredr
# Expected: 'AVAILABLE AVAILABLE AVAILABLE AVAILABLE AVAILABLE'
ok 15
[3683] rendering error track: gdImageGd2Ptr error at /usr/share/
GD Warning: GD2 image support has been disabled
gdImageGd2Ptr error at /usr/share/
Dubious, test returned 25 (wstat 6400, 0x1900)
Failed 10/19 subtests
Similar failures are seen in Debian's test logs for the package:
https:/
This appears to match this bug in Debian:
https:/
Which in turn is forwarded upstream here:
https:/
No solution has been proposed as of this time, near as I can tell. Unfortunately, upstream seems to not be actively committing to the codebase for some years. Bug #64 speculates the problem may be due to some removed formats in libgd3; if true, then perhaps one option could be to disable the corresponding test cases?
Changed in gbrowse: | |
status: | Unknown → New |
Changed in gbrowse (Debian): | |
status: | Unknown → Confirmed |
Changed in gbrowse (Debian): | |
status: | Confirmed → Fix Released |
The autopkgtests are passing now:
https:/ /autopkgtest. ubuntu. com/packages/ gbrowse