Let me know what may be needed. The report says "failures: 2" and the final
message at the bottom says "1 of 1 test failed".
I think that the test results are a "fail" also but that is just an opinion.
Seems to be a well known bug regardless :
FAIL: threads.test: mutex-ownership:
Hi guilers,
I've mentioned these to Mark Weaver on IRC off-hand before, but I'm
posting this bug report to "formalise" it, and make sure we don't
forget.
Peter Bex, as one of the maintainers of the chicken "numbers" egg,
created a thorough test suite for string->number a while ago[0], and it
poi
Hi,
Dennis Clarke skribis:
> FAIL: gc.test: gc: Lexical vars are collectable
[...]
> FAIL: threads.test: mutex-ownership: mutex with owner not retained (bug
> #27450)
These two tests are GC-sensitive, so unfortunately failure rarely
indicates a problem. IOW, it is safe to ignore them.
Whic
Hi Bernardo,
Bernardo Ezequiel Contreras skribis:
> FAIL: test-scm-spawn-thread
> /bin/bash: line 5: 2329 Segmentation fault srcdir="."
> builddir="."
> CHARSETALIASDIR="/home/vonbecmann/downloads/guile/guile-2.0.6/lib"
> GUILE_AUTO_COMPILE=0 "../../meta/uninstalled-env" ${dir}$tst
> FAIL
Hi,
gnuemacser skribis:
>?: 0 [primitive-load-path
> "e:\\temp\\files\\guile\\guile-2.0.6\\build\\libguile/e:/temp/files/guile/guile-2.0.6/build/meta/guild"]
[...]
> the error is as same as
> https://lists.gnu.org/archive/html/bug-guile/2012-01/msg00056.html
Can you point us to the patc
> Hi,
>
> Dennis Clarke skribis:
>
> > FAIL: gc.test: gc: Lexical vars are collectable
>
> [...]
>
> > FAIL: threads.test: mutex-ownership: mutex with owner not retained
> (bug #27450)
>
> These two tests are GC-sensitive, so unfortunately failure rarely
> indicates a problem. IOW, it is sa
Hi,
Dennis Clarke skribis:
>> Dennis Clarke skribis:
>>
>> > FAIL: gc.test: gc: Lexical vars are collectable
>>
>> [...]
>>
>> > FAIL: threads.test: mutex-ownership: mutex with owner not retained
>> (bug #27450)
>>
>> These two tests are GC-sensitive, so unfortunately failure rarely
>> ind
> > Not sure how to get your libC version
>
> IIRC “dpkg -l libgc” should tell you.
$ dpkg -l libgc
No packages found matching libgc.
hrmmm ... let me dig around in there
Dennis
Hi Ludo,
here's the output
$ dpkg -l libgc-dev
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-=
- Original Message -
From: l...@gnu.org (Ludovic Courtès)
Date: Monday, July 9, 2012 12:47 pm
Subject: Re: bug#11885: guile-2.0.6 1 of 1 test failed
To: Dennis Clarke
Cc: 11...@debbugs.gnu.org
> >
> >> Which GCC optimization options, and which libgc version do you use?
>
> [...]
>
>
10 matches
Mail list logo