[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MinGW vs. setlocale

From: Ludovic Courtès
Subject: Re: MinGW vs. setlocale
Date: Thu, 19 Jun 2014 10:16:51 +0200
User-agent: Gnus/5.130009 (Ma Gnus v0.9) Emacs/24.3 (gnu/linux)

Doug Evans <address@hidden> skribis:

> On Jun 11, 2014 3:14 PM, "Ludovic Courtès" <address@hidden> wrote:
>> Eli Zaretskii <address@hidden> skribis:
>> >> [...]
>> >   UNRESOLVED: i18n.test: string mapping: string-locale-downcase Turkish
>> >
>> > I don't know why these fail.
>> Note that “UNRESOLVED” is not a failure; it means “we can’t run this
>> test here, so skip it.”
> Hi.
> At least in GDB, I generally infer UNRESOLVED to mean "action needed"
> (could be test harness bug or some such), whereas if a test can't be run in
> a particular config I see UNSUPPORTED which I infer to mean "no action
> needed".

Yes, that makes sense, but for historical reasons (perhaps a historical
misunderstanding? ;-)), Guile’s test suite has been using “UNRESOLVED”
with the meaning above.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]