bug-bison
[Top][All Lists]
Advanced

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

cygwin testsuite failure


From: Eric Blake
Subject: cygwin testsuite failure
Date: Fri, 11 Jul 2008 19:34:03 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

With cygwin 1.5.25 and all pre-built cygwin packages installed, I get the
following failure on bison 2.3b+ and m4 1.4.11: (full log attached,
relevant portion clipped here)

## ---------------------- ##
## Detailed failed tests. ##
## ---------------------- ##

#                             -*- compilation -*-
49. output.at:188: testing ...
./output.at:188: bison -o "address@hidden&*()-=_+{}[]|\\:;<>, .'.c"
- --defines="\`~!@
#\$%^&*()-=_+{}[]|\\:;<>, .'.h" glr.y
Not enabling shell tracing (command contains a `...` command substitution)
- --- /dev/null   2006-11-30 17:00:00.000000000 -0700
+++ /home/eblake/bison/tests/testsuite.dir/at-groups/49/stderr  2008-07-11
14:54
:18.921875000 -0600
@@ -0,0 +1 @@
+/home/eblake/bison/src/bison: cannot open file
address@hidden&*()-=_+{}[]|\:;<>, .'.
c': No such file or directory
./output.at:188: exit code was 1, expected 0
49. output.at:188: 49. Output file name: address@hidden&*()-=_+{}[]|\:;<>, .'
(output.
at:188): FAILED (output.at:188)

On cygwin, \ is an (alternate) directory separator, and since
"address@hidden&*()-=_{}[]|" isn't a directory, that explains the ENOENT failure
for the file "\:;<>, .".  For that matter, if I don't use a cygwin managed
mount, then there are additional restrictions enforced by Windows (at
least {}<> are also invalid, : is iffy, and trailing . is silently
stripped).  Since this test is relying on a non-portable file name, it is
probably easiest to just make it skip if the file doesn't work for the
current file system.  Another option would be borrowing from autoconf's
testsuite, which determines which characters are invalid for the current
file system, then comes up with a maximal string of remaining line noise
characters to run the test rather than skipping it.

I'll have results on cygwin 1.7.0 later; there I had an additional failure
(I don't remember which at the moment), but that may have been due to
fewer cygwin packages being installed.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkh4CgsACgkQ84KuGfSFAYBBZwCgrdfQ+kn7RRy0rMhsW/OuqGYi
22oAnReRVoAYJQd0/DCIEfXQQhE87jdU
=1hXh
-----END PGP SIGNATURE-----

Attachment: testsuite.log.lzma
Description: Binary data


reply via email to

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