| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Fix all the tests that were using quotes, and (by implication) working
because barewords are treated as strings, and one-liners aren't run under
strict.
|
| |
|
| |
|
| |
|
|
|
|
| |
Not very elegant, but it avoids using $^W or warnings.pm.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When porting/makerel runs, all files copied into the directory for the
tarball have the executable bit stripped and then only a specific set of
files have the executable bit restored.
There are many files in the repo that have the executable bit set in the
repo that will be stripped. So that the state of files in the repo is
as close as possible to the state of files in the release tarball, the
executable bit has been stripped from such files.
In one recent case, a file added from a dual-life module needed the
executable bit set. Because it had the bit in the repo but was
not listed in makerel to get an executable bit, tests using it
passed in the repo and failed in the tarball.
This commit refactors the list into a new file, Porting/exec-bit.txt
and add tests to detect a mismatch between files listed there
and actual executable bits in the repo.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* The default watchdog strategy on Win32 doesn't work because the watchdog
is executed via subshell ("cmd /c perl -e '...'"). When the test finishes
and tries to kill the watchdog all it manages to do is whack cmd.exe and
the watchdog still fires, potentially killing an innocent process.
* Trying to use the fork() strategy instead causes openpid.t's test #9's
"ok" to be lost occasionally. The message itself is generated by the 4th
child of the test and should go directly to stdout, but sometimes the
output vanishes for unexplained reasons. This doesn't appear to happen
without the watchdog enabled.
* Using the alarm() watchdog strategy seems to not cause any badness.
|
|
|
|
| |
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds functions native_to_latin1($) and latin1_to_native($) to
test.pl. Use of these in test scripts allows for less special case code
(or deciding to blow it off and just skip EBCDIC platforms). If a
string is all ASCII, one has always been able to just use it and not
worry about EBCDIC. But non-ASCII, latin1 characters have been a
different matter. This allows one to wrap those characters in a
function call and get automatic EBCDIC compatibility.
The functions do not handle UTF-8/UTF-EBCDIC conversions. This is more
complicated, and I was worried that that part was not appropriate for
test.pl which should use the bare minimum of Perl functionality. These
functions use tr///, beyond what other parts of test.pl use.
|
|
|
|
| |
It's optional and this was causing test failures when it didn't exist.
|
|
|
|
|
|
|
|
|
|
| |
The existing code does the wrong thing if a string (rather than a compiled
regexp) is supplied for $expected. Happily perl will do the right thing
if you let it.
Hugo
Message-Id: <200912041444.nB4EiqBj004436@zen.crypt.org>
|
| |
|
|
|
|
|
| |
It was inserting a newline in the command string, which
causes a syntax error (at least on VMS).
|
|
|
|
|
|
| |
This was the only use of scalar references in test.pl, and the only use of \
to create a reference to a scalar. We are now more robust in the face of parser
or runtime bugs.
|
|
|
|
|
|
| |
{} could be misparsed, ++ has a lot of internal implementation "magic" that we
don't need, but don't want to trip us up if it isn't working, and op= isn't
necessary when we already rely on the more general $a = $b op $c working.
|
| |
|
| |
|
|
|
|
| |
does the result so tests don't weirdly fail just because the author didn't realize it was normalizing newlines.
|
|
|
|
|
| |
even more tests if use is borked, but not require.
p4raw-id: //depot/perl@34528
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510809230640y2d5a072g6abff6604f9daa79@mail.gmail.com>
p4raw-id: //depot/perl@34434
|
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510809090654v2de48f1r37499d573f452cdb@mail.gmail.com>
Date: Tue, 9 Sep 2008 09:54:41 -0400
p4raw-id: //depot/perl@34337
|
|
|
|
|
|
|
| |
(such as when an alarm fires). Also, bail out with SIGTERM rather
than SIGKILL on VMS since the latter kills the shell from which
Perl was started.
p4raw-id: //depot/perl@34316
|
|
|
|
|
|
|
|
| |
Also we need to note file names we give out, as some callers don't
create them before calling us a second time.
Add a regexp that matches the tempfile() names, for tests that want to
munge output.
p4raw-id: //depot/perl@34179
|
|
|
| |
p4raw-id: //depot/perl@34178
|
|
|
|
|
|
| |
names clashing between different scripts, which may now be executing
in parallel)
p4raw-id: //depot/perl@34173
|
|
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510807230919p355ea37ci3fde2c1f84df6d5f@mail.gmail.com>
Adds a needed diag message to the watchdog() function for MSWin32.
p4raw-id: //depot/perl@34154
|
|
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510807180609l7ca8a8d8i653dfd687ed9f36d@mail.gmail.com>
Changes skip messages to be consistent with Test::Builder.
p4raw-id: //depot/perl@34152
|
|
|
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510807110807hb3e3727la161367a63da607f@mail.gmail.com>
Jerry found that localizing $? doesn't shield the effects of wait()
unless you actually assign something to $?
p4raw-id: //depot/perl@34147
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510807071029q5931f03ud506f06b7d1f72af@mail.gmail.com>
p4raw-id: //depot/perl@34109
|
|
|
|
|
|
| |
to keep to simple constructions to facilitate accurately testing the
core interpreter, which might be buggy.
p4raw-id: //depot/perl@34097
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510806281218i65d32061w27a4431b9b357107@mail.gmail.com>
p4raw-id: //depot/perl@34091
|
|
|
|
|
| |
Message-ID: <477AF314.9050808@pobox.com>
p4raw-id: //depot/perl@32801
|
|
|
|
|
|
| |
From: "Jerry D. Hedden" <jdhedden@cpan.org>
Message-ID: <1ff86f510712111035u7f8da6e8h1a1cbd9d85d27c03@mail.gmail.com>
p4raw-id: //depot/perl@32611
|
|
|
|
|
| |
Message-ID: <46F59EFE.7050303@ztreet.demon.nl>
p4raw-id: //depot/perl@31962
|
|
|
| |
p4raw-id: //depot/perl@30855
|
|
|
|
|
|
| |
hard value, so that callers of like and unlike can present diagnostics
with the line number of their own caller.
p4raw-id: //depot/perl@30344
|
|
|
|
|
| |
in PATH on VMS (and scrubbing them in t/test.pl).
p4raw-id: //depot/perl@28348
|
|
|
| |
p4raw-id: //depot/perl@28059
|
|
|
|
|
|
|
|
| |
Message-ID: <4456120B.3000302@landgren.net>
Plus some additional comment (also from David) about WHY not to
use ++ in test.pl
p4raw-id: //depot/perl@28037
|
|
|
|
|
|
| |
My system is set up with a few PATH entries I'm not allowed
to access, so stat() fails for these.
p4raw-id: //depot/perl@27551
|
|
|
|
|
| |
The stripping was introduced in change 27364 to improve taint handling.
p4raw-id: //depot/perl@27550
|
|
|
|
|
|
| |
- better taint detection (switch -T in command)
- $ENV{PATH} stripping of writeable directories on unix/linux
p4raw-id: //depot/perl@27364
|
|
|
| |
p4raw-id: //depot/perl@27345
|
|
|
|
|
| |
really wanted to run perl, so brute force untaint everything.
p4raw-id: //depot/perl@27220
|
|
|
| |
p4raw-id: //depot/perl@26469
|
|
|
|
|
|
|
|
| |
it's an unexpected success
Subject: Re: Change 26165 broke ext/threads/t/stress_re.t test on Win32 (and patch to t/test.pl and/or Test::Harness)
Message-ID: <9b18b3110512170823q1bb2cd27h838b4d4dcdba72c9@mail.gmail.com>
p4raw-id: //depot/perl@26398
|
|
|
|
|
|
|
|
| |
- Adjust the regression tests to use t/test.pl from bleadperl
when $ENV{PERL_CORE} is defined
- Add can_ok and isa_ok to t/test.pl from the implementation
found in the IO CPAN distribution
p4raw-id: //depot/perl@25355
|
|
|
|
|
| |
Message-ID: <20050722185115.GB28829@windhund.schwern.org>
p4raw-id: //depot/perl@25252
|
|
|
|
|
| |
this can be useful to use valgrind for example
p4raw-id: //depot/perl@24856
|