-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED) #7573
Comments
From @ysthext/Cwd/t/cwd.............................readdir(linktest/..): No such file or directory at ../ext/Cwd/t/cwd.t line 151 The io/tell doesn't concern me; it's a questionable test, and goes away ext/Cwd/t/cwd turns out to happen with older perls with the Cwd from CPAN ext/B/t/optree_specials seems to be expecting stderr/stdout to have a Perl Info
|
From @nwc10Thanks for the report. Better to know about these things before a release On Mon, Nov 01, 2004 at 07:50:30PM -0000, Yitzchak Scott-Thoennes wrote:
Did cygwin fail with Cwd 2.21 (or whatever the most recent version you tried
This seems to be the same problem as is being described for VMS. |
The RT System itself - Status changed from 'new' to 'open' |
From @ysthOn Mon, Nov 01, 2004 at 08:13:14PM +0000, Nicholas Clark wrote:
This was with perl5.8.4 and Cwd 2.21 testing with TEST_PERL_CWD_CODE set.
Apparently I rsynced just before you upgraded to 3.01. .patch is 23451, and lib/Cwd.pm says $VERSION = '2.21'. I'll try again. |
From @ysthOn Mon, Nov 01, 2004 at 12:27:41PM -0800, Yitzchak Scott-Thoennes wrote:
Or rather, I didn't realize PathTools existed :) Same error with perl5.8.4 and PathTools 3.01. |
From @nwc10On Mon, Nov 01, 2004 at 12:31:50PM -0800, Yitzchak Scott-Thoennes wrote:
I didn't until yesterday.
This seems to be the same problem that Merijn found. It worked for him if http://pastebot.nd.edu/1058 I don't know what this tells us. Nicholas Clark |
From @TuxOn Mon 01 Nov 2004 20:50, Yitzchak Scott-Thoennes (via RT) <perlbug-followup@perl.org> wrote:
Isn't that the same I reported from blead? This one went away if I symlinked cwt.t to perl_current/t
-- |
From @ysthOn Mon, Nov 01, 2004 at 11:21:27PM +0100, H.Merijn Brand wrote:
I see this report from July: Is there some other one?
Can you be more specific? |
From @TuxOn Mon 01 Nov 2004 23:35, Yitzchak Scott-Thoennes <sthoenna@efn.org> wrote:
On my other pc: ../ext/Cwd/t/cwd............................ok 20/27readdir(linktest/..): No such file or directory at ../ext/Cwd/t/cwd.t line 151 Failed Test Stat Wstat Total Fail Failed List of Failed ../ext/Cwd/t/cwd.t 1 256 27 1 3.70% 21 That was line 151. That was from make test_harness Now a manual run ... PC09:/P/perl-current 506 $ perl -Ilib ext/Cwd/t/cwd.t and then make the symlink and run again: PC09:/P/perl-current 507 $ ln -s ../ext/Cwd/t/cwd.t t/ which is what I posted in http://pastebot.nd.edu/1058 I'm so glad I can still reproduce it all :) -- |
From @ysthOn Tue, Nov 02, 2004 at 01:44:46AM +0100, "H.Merijn Brand" wrote:
This is all as expected. You aren't setting PERL_CORE, so it skips 3
|
From @ysthOn Mon, Nov 01, 2004 at 08:45:33PM +0000, Nicholas Clark wrote:
Ok, I think you at least can ignore this, Nicholas. The problem exists In any case, the failure is only for _perl_abs_path which won't ever BTW, I await with eager expectation the quote in the RC1 release |
From @ysthOn Mon, Nov 01, 2004 at 07:50:30PM -0000, Yitzchak Scott-Thoennes wrote:
Here's a patch to skip it. It isn't actually needed on blead (where Inline Patch--- perl/t/io/tell.t.orig 2003-08-30 12:56:58.000000000 -0700
+++ perl/t/io/tell.t 2004-11-09 17:24:51.044630400 -0800
@@ -148,7 +148,13 @@
close $tst;
open($tst,">>$written") || die "Cannot open $written:$!";
+# This test makes a questionable assumption that the file pointer will
+# be at eof after opening a file but before seeking, reading, or writing.
+# Only known failure is on cygwin.
+my $skip = $^O eq "cygwin" && &PerlIO::get_layers($tst) eq 'stdio'
+ && ' # skip: file pointer not at eof';
+
if (tell($tst) == 6)
-{ print "ok 28\n"; } else { print "not ok 28\n"; }
+{ print "ok 28$skip\n"; } else { print "not ok 28$skip\n"; }
close $tst;
End of Patch. |
From @rgsYitzchak Scott-Thoennes wrote:
Thanks, applied as #23491 to bleadperl.
|
@rgs - Status changed from 'open' to 'resolved' |
From @ysthOn Tue, Nov 09, 2004 at 05:40:13PM -0800, Yitzchak Scott-Thoennes <sthoenna@efn.org> wrote:
Sorry, that was not the patch I meant to send; this one actually works: Inline Patch--- perl/t/io/tell.t.orig 2003-08-30 12:56:58.000000000 -0700
+++ perl/t/io/tell.t 2004-11-10 01:09:05.819828800 -0800
@@ -148,7 +148,13 @@
close $tst;
open($tst,">>$written") || die "Cannot open $written:$!";
+# This test makes a questionable assumption that the file pointer will
+# be at eof after opening a file but before seeking, reading, or writing.
+# Only known failure is on cygwin.
+my $todo = $^O eq "cygwin" && &PerlIO::get_layers($tst) eq 'stdio'
+ && ' # TODO: file pointer not at eof';
+
if (tell($tst) == 6)
-{ print "ok 28\n"; } else { print "not ok 28\n"; }
+{ print "ok 28$todo\n"; } else { print "not ok 28$todo\n"; }
close $tst;
End of Patch. |
From @rgsYitzchak Scott-Thoennes wrote:
OK, TODO and not SKIP, as you wish (applied as #23492.) |
Migrated from rt.perl.org#32272 (status was 'resolved')
Searchable as RT32272$
The text was updated successfully, but these errors were encountered: