Package: guile-2.2 / 2.2.6+1-1

Metadata

Package Version Patches format
guile-2.2 2.2.6+1-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
0001 Mark mutex with owner not retained threads test as u.patch | (download)

test-suite/tests/threads.test | 6 4 + 2 - 0 !
1 file changed, 4 insertions(+), 2 deletions(-)

 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.

0002 Look for guile procedures.txt in pkglibdir.patch | (download)

module/ice-9/documentation.scm | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

 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.

Bug: https://debbugs.gnu.org/22833
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816123

0003 Disable sandbox.test 1e6 alloc loop allocation limit.patch | (download)

test-suite/tests/sandbox.test | 6 4 + 2 - 0 !
1 file changed, 4 insertions(+), 2 deletions(-)

 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.

0004 Disable intermittently failing test out of memory te.patch | (download)

test-suite/standalone/test-out-of-memory | 10 5 + 5 - 0 !
1 file changed, 5 insertions(+), 5 deletions(-)

 disable intermittently failing test-out-of-memory test for now

After checking with upstream, disable a test-out-of-memory test that
appears to have been causing a FTBS on a number of architectures.

(Running test-suite/standalone/test-out-of-memory in a loop reproduces
 the problem very quickly on amd64 here.)

Bug-Debian: https://bugs.debian.org/880148

0005 Disable more of test out of memory test.patch | (download)

test-suite/standalone/test-out-of-memory | 14 7 + 7 - 0 !
1 file changed, 7 insertions(+), 7 deletions(-)

 disable more of test-out-of-memory test


0006 gc.test after gc hook mark unresolved on failure eve.patch | (download)

test-suite/tests/gc.test | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 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.

Bug: https://debbugs.gnu.org/31776
Bug-Debian: https://bugs.debian.org/900652