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.

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

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.

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

test-suite/standalone/Makefile.am | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 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.

Bug: https://debbugs.gnu.org/29464
Bug-Debian: https://bugs.debian.org/880148
Bug-Debian: https://bugs.debian.org/966300

test-suite/tests/numbers.test | 19 16 + 3 - 0 !
1 file changed, 16 insertions(+), 3 deletions(-)

 numbers.test: disable unresolved "mixed type" division tests on i686

Bug: https://debbugs.gnu.org/43262
Bug-Debian: https://bugs.debian.org/968403

test-suite/tests/ports.test | 7 4 + 3 - 0 !
1 file changed, 4 insertions(+), 3 deletions(-)

 fix "non-revealed port is closed" ports.test

Don't close the test port's file descriptor because the port still has a
reference to it, and could still close it at any time when finally
garbage collected.  This did soemetimes break subsequent tests.

Bug: https://debbugs.gnu.org/43521

test-suite/tests/asyncs.test | 73 38 + 35 - 0 !
1 file changed, 38 insertions(+), 35 deletions(-)

 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.

Bug: https://debbugs.gnu.org/46001
Bug-Debian: https://bugs.debian.org/980498

bootstrap/Makefile.am | 9 8 + 1 - 0 !
configure.ac | 3 3 + 0 - 0 !
stage0/Makefile.am | 10 9 + 1 - 0 !
3 files changed, 20 insertions(+), 2 deletions(-)

 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.

Bug: https://debbugs.gnu.org/45214
Bug-Debian: https://bugs.debian.org/977223