See note below about an issue where I may have some corrupted files
affecting the test results.
EAGLE> search blead_test.log fail
t/run/exit................................FAILED at test 3
t/run/switches............................FAILED
--unexpected output at test 15
t/op/goto.................................FAILED at test 53
t/op/gv...................................FAILED at test 67
t/op/magic................................FAILED at test 7
t/op/pack.................................FAILED
--unexpected output at test 0
t/lib/vmsfspec............................FAILED
--unexpected output at test 62
ext/B/t/assembler.........................FAILED
--unexpected output at test 0
ext/Compress/Zlib/t/03examples............FAILED at test 1
ext/Compress/Zlib/t/06gzdopen.............FAILED
--unexpected output at test 0
ext/Devel/Peek/t/Peek.....................FAILED
--unexpected output at test 20
ext/Digest/MD5/t/files....................FAILED
--unexpected output at test 0
ext/POSIX/t/sigaction.....................FAILED
--expected 30 tests, saw 27
lib/Archive/Tar/t/02_methods..............FAILED
--unexpected output at test 68
lib/bignum/t/bninfnan.....................FAILED
--unexpected output at test 0
lib/Config/Extensions.....................FAILED
--unexpected output at test 0
lib/ExtUtils/ParseXS/t/basic..............FAILED
--unexpected output at test 3
lib/ExtUtils/t/basic......................FAILED at test 67
lib/ExtUtils/t/Constant...................FAILED at test 27
lib/ExtUtils/t/FIRST_MAKEFILE.............FAILED at test 4
lib/ExtUtils/t/PL_FILES...................FAILED at test 3
lib/File/Copy.............................FAILED at test 20
lib/File/Spec/t/Spec......................FAILED
--unexpected output at test 210
lib/Math/BigInt/t/mbi_rand................FAILED
--unexpected output at test 4
lib/Test/Simple/t/create..................FAILED at test 7
Failed 25 test scripts out of 919, 97.28% okay.
Abe Timmerman wrote:
My build just died because it can not figure out how to create
pod/perlcygwin.pod. As near as I can tell, that file was supposed to be
in the distribution, but rsync does not report it as available for
download, and it is not in the MANIFEST. file.
Unlike pod/perlvms.pod (which is copied from vms/perlvms.pod); all the other
pod/perl<os>.pod files are generated (copied) from README.<os> during the
build process
Now that I know that, I can chase that down, so it does help a lot.
In the case of OpenVMS, the step is done as part of CONFIGURE.COM.
The actual problem is that due to a bug in the experimental pthread
rsync (which is the only one I have a VMS binary for), it occasionally
corrupts files, and refuses to replace those corrupted files until they
are manually deleted. This file makes it three files that were
corrupted so far. In these cases the entire file has usually been
replaced with a different one, and it seems to like replacing the
contents of the file with a changelog file.
Usually the compiler finds these. In this case the readme.cygwin was
corrupted on the rsync copy, and as such, configure.com did not select
it for extraction.
It is possible that these corruptions are responsible for some of the
test failures, but I really will not know until at least tonight if I
get the time. I am real suspicious of the ones that failed at test 0.
But this should give you the information needed to get this far.
-John
[EMAIL PROTECTED]
Personal Opinion Only
