It looks like gc.test may be failing intermittently in Debian (see below). Searching around I saw at least one other report of this in the #guile logs from last year.
For now, I'm wondering if if would be plausible to mark the test as unresolved to avoid guile-2.2's removal from Debian testing, or if the failure is likely to indicate a problem serious enough to warrant that removal. Emilio Pozuelo Monfort <po...@debian.org> writes: > Your package failed to build on armhf: > > Running gc.test > FAIL: gc.test: gc: after-gc-hook gets called > [...] > Totals for this test run: > passes: 40732 > failures: 1 > unexpected passes: 0 > expected failures: 10 > unresolved test cases: 578 > untested test cases: 1 > unsupported test cases: 1 > errors: 0 > > FAIL: check-guile > ================================== > 1 of 1 test failed > > > Full log at https://buildd.debian.org/status/package.php?p=guile-2.2 Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
