bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called

2018-08-06 Thread Göran Weinholt
Rob Browning writes: > Rob Browning writes: > >> Rob Browning writes: >> >>> 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

bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called

2018-07-19 Thread Rob Browning
Rob Browning writes: > Rob Browning writes: > >> 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

bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called

2018-06-16 Thread Rob Browning
Rob Browning writes: > 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

bug#31776: guile-2.2: FTBFS on armhf: FAIL: gc.test: gc: after-gc-hook gets called

2018-06-10 Thread Rob Browning
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,