Re: [PATCH 14/13] wildmatch: fix tests that fail on Windows due to path mangling
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Nov 7, 2012, 19:32 UTC
- Message-ID
- <509AB76A.3070700@kdbg.org>
- In-Reply-To
- <CACsJy8DEH53mA4fDyZwbVsbyGcNY8b54Sn1p5-rto6r_h48dkA@mail.gmail.com>
Am 06.11.2012 13:47, schrieb Nguyen Thai Ngoc Duy:
Show 7 quoted lines
> On Mon, Nov 5, 2012 at 4:00 AM, Johannes Sixt <j6t@kdbg.org> wrote: >> Patterns beginning with a slash are converted to Windows paths before >> test-wildmatch gets to see them. Use a different first character. > > Or we could prepend the paths with something, which is then cut out by > test-wildmatch. Not sure if it's intuitive to look at the tests > though.
That would be a possibility, too.
>> After this change, there are still 3 failing tests that are in connection >> with [[:xdigit:]]. Don't know, yet, what's going on there. > > the wildmatch tests or fnmatch ones?
fnmatch ones:
ok 147 - wildmatch: match '5' '[[:xdigit:]]' not ok 148 - fnmatch: match '5' '[[:xdigit:]]' # # test-wildmatch fnmatch '5' '[[:xdigit:]]' # ok 149 - wildmatch: match 'f' '[[:xdigit:]]' not ok 150 - fnmatch: match 'f' '[[:xdigit:]]' # # test-wildmatch fnmatch 'f' '[[:xdigit:]]' # ok 151 - wildmatch: match 'D' '[[:xdigit:]]' not ok 152 - fnmatch: match 'D' '[[:xdigit:]]' # # test-wildmatch fnmatch 'D' '[[:xdigit:]]' #
She same tests fail on Linux, BTW, when built with NO_FNMATCH=1 and the "#if defined _LIBC || !defined __GNU_LIBRARY__" brackets removed.
-- Hannes