| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Mark-mutex-with-owner-not-retained-threads-test-as-u.patch | Mark "mutex with owner not retained" threads test as unresolved. As per discussion with upstream, mark this test as unresolved since it may produce false negatives, depending on the behavior/timing of the garbage collector. |
Rob Browning <rlb@defaultvalue.org> | no | 2012-03-18 | ||
| 0002-Look-for-guile-procedures.txt-in-pkglibdir.patch | Look for guile-procedures.txt in pkglibdir Look for guile-procedures.txt in %guile-build-info's pkglibdir first since the content is not architecture independent. |
Rob Browning <rlb@defaultvalue.org> | yes | debian upstream | 2016-08-12 | |
| 0003-Disable-sandbox.test-1e6-alloc-loop-allocation-limit.patch | Disable sandbox.test "1e6 alloc loop" "allocation limit" test The test suite would eventually hang on sandbox.test when run in a "make -j5 check" loop. The last test printed to the log was the one before "1e6 alloc loop", and after commenting out that test, the loop doesn't appear to hang, so disable it for now. |
Rob Browning <rlb@defaultvalue.org> | no | 2018-02-20 | ||
| 0004-gc.test-after-gc-hook-mark-unresolved-on-failure-eve.patch | gc.test: after-gc-hook - mark unresolved on failure (everywhere) Previously this was done for just mips and mipsel, 59d9bcd468aab0d97d763595fd4e934044dc7590 "gc.test: after-gc-hook - mark unresolved on failure for mips(el)", and then fd4ba18bca1c6000fc0dd417a5b489e1ac60e0d9 "Fix gc.test "after-gc-hook gets called" failures" attempted to fix it upstream, but as of 2.2.6 it's failing again, this time on amd64, so just mark it as unresolved everywhere for now. |
Rob Browning <rlb@defaultvalue.org> | yes | debian upstream | 2019-09-01 | |
| 0005-Mark-test-out-of-memory-as-an-expected-failure-for-n.patch | Mark test-out-of-memory as an expected failure for now Since this test has been failing for a long time on various architectures, mark it as expected to fail for now so that we'll still run it and can see the results, but won't be blocked by it. There are known issues with the test upstream, and at least in some past cases it's been possible to reproduce the failure quickly by running test-suite/standalone/test-out-of-memory in a loop. |
Rob Browning <rlb@defaultvalue.org> | yes | debian upstream | 2018-02-20 | |
| 0006-numbers.test-disable-unresolved-mixed-type-division-.patch | numbers.test: disable unresolved "mixed type" division tests on i686 | Rob Browning <rlb@defaultvalue.org> | yes | debian upstream | 2020-09-12 | |
| 0007-Mark-preemption-via-sigprof-test-as-an-expected-fail.patch | Mark "preemption via sigprof" test as an expected failure for now Since this test fails intermittently in earlier versions (e.g. 3.0.4), and after discussion upstream, mark it as unresolved so that we'll still run it and can see the results, but won't be blocked by it. |
Rob Browning <rlb@defaultvalue.org> | yes | debian upstream | 2018-02-20 | |
| 0008-Fix-32-bit-big-endian-builds-via-Oresolve-primitives.patch | Fix 32-bit big endian builds via -Oresolve-primitives -Ocps Specify -Oresolve-primitives -Ocps during bootstrapping builds to fix build failures on 32-bit big endian architectures. Thanks to John David Anglin for reporting the problem and investigating the problem, and to John Paul Adrian Glaubitz for helping devise the solution. |
Rob Browning <rlb@defaultvalue.org> | yes | debian upstream | 2018-02-20 |