At 12:26 AM -0500 11/6/01, Michael G Schwern wrote:
>I keep getting:
>
>$ MCR SYS$DISK:[]perl. -"Ilib" op/my_stash.t
If you use the Unix filename syntax, you'll need to wrap the filespec
in double quotes, but that's not your immediate problem.
>%DCL-W-ACTIMAGE, error activating image PERLSHR
>-C
On Mon, Nov 05, 2001 at 10:23:42PM -0600, Craig A. Berry wrote:
> >PS What's the VMS equivalent of:
> >
> >./perl -Ilib t/op/my_stash.t
>
> $ MCR SYS$DISK:[]perl. -"Ilib" [.t.op]my_stash.t
>
> or
>
> $ MCR SYS$DISK:[]perl. -"Ilib" "t/op/my_stash.t"
>
> or, from within Perl
I keep getting
In article , "Craig A. Berry"
<[EMAIL PROTECTED]> wrote:
> BTW, when running tests you're generally in the t directory, aren't you, so
> wouldn't it just be "op/my_stash.t"?
Not necessarily. Lots of tests start with:
BEGIN {
chdir 't
I'm working on taking test.com and merging it's differences into
t/TEST so vms/test.com just becomes a thin DCL wrapper around t/TEST.
One of the major differences is test.com itself skips a heap of tests
because they don't work on VMS, but the operators often do. So I'm
doing two things:
1
In article <[EMAIL PROTECTED]>, "H . Merijn Brand"
<[EMAIL PROTECTED]> wrote:
> HP-UX 10.20:
>
> k1:/pro/3gl/CPAN/libnet-1.09 119 > perl -Iblib/arch -Iblib/lib t/config.t
> 1..10
> not ok 4 # ... should return -1 without a valid hostname Got: '0' Expected:
> '-1'
> main t/config.t 2
=head1 NAME
Perl Core Smoke Test Suite
=head1 SYNOPSIS
# at 22:25
sh smoke.sh [/usr/CPAN/perl-current [smoke.cfg]]
#
or for the brave and trustworthy
# perl Makefile.PL
=head1 DESCRIPTION
The perl core smoke test suite is a set of simple scripts that try to
run the perl core tests
On Mon 05 Nov 2001 15:50, Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> > > (1) How about looking for my snapshot announcements in p5p
> > > (or "patchlevel.h" updates in perl5-changes) and launching smokes
> > > from them, not from some arbitrary points in time?
> > >
> > > (2) Add a (cronjob?)
> > (1) How about looking for my snapshot announcements in p5p
> > (or "patchlevel.h" updates in perl5-changes) and launching smokes
> > from them, not from some arbitrary points in time?
> >
> > (2) Add a (cronjob?) suspend-all option to the smoke harness:
> > basically, send a SIGSTOP signal fo
On Mon, Nov 05, 2001 at 03:05:23PM +0100, H.Merijn Brand wrote:
> On Mon 05 Nov 2001 15:00, Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> > > Automated smoke report for patch 12847
> >
> > Fixed in 12848. Your smokes seem always to pick the most inconvenient
> > spot :-)
>
> Blame it to time d