unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Terry Phelps <tgphelps50@gmail.com>
To: 54163@debbugs.gnu.org
Subject: bug#54163: guile 3.0.8 'make check' fails
Date: Fri, 25 Feb 2022 13:05:28 -0500	[thread overview]
Message-ID: <CAMUfR_stzBtLvweJim56h240jEnhPmjLrU=3dTHM6jgGSP4pvQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

I just got the 3.0.8 tarball and did a build on Fedora 35 x64. I used no
parameters to 'configure', except for '--prefix'. Then I did 'make' and
'make check'.

One test failed. The output ends with:

wrote
`/home/tgphelps/guile-3.0.8/cache/guile/ccache/3.0-LE-8-4.6/home/tgphelps/guile-3.0.8/test-suite/standalone/test-stack-overflow.go'
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
allocate_stack failed: Cannot allocate memory
PASS: test-stack-overflow
wrote
`/home/tgphelps/guile-3.0.8/cache/guile/ccache/3.0-LE-8-4.6/home/tgphelps/guile-3.0.8/test-suite/standalone/test-out-of-memory.go'
GC Warning: Failed to expand heap by 134742016 bytes
GC Warning: Failed to expand heap by 134217728 bytes
GC Warning: Out of Memory! Heap size: 2 MiB. Returning NULL!
error creating finalization thread: Cannot allocate memory
mmap(PROT_NONE) failed
FAIL: test-out-of-memory
==================================
1 of 40 tests failed
Please report to bug-guile@gnu.org
==================================

If you want more information, just ask.

[-- Attachment #2: Type: text/html, Size: 1480 bytes --]

             reply	other threads:[~2022-02-25 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 18:05 Terry Phelps [this message]
2022-02-26 15:18 ` bug#54163: guile 3.0.8 'make check' fails Vijay Marupudi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMUfR_stzBtLvweJim56h240jEnhPmjLrU=3dTHM6jgGSP4pvQ@mail.gmail.com' \
    --to=tgphelps50@gmail.com \
    --cc=54163@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).