On Tue, 19 Jun 2007, Andy Dougherty wrote:
> On Mon, 18 Jun 2007, chromatic via RT wrote:
>
> > On Monday 18 June 2007 09:54:01 Andy Dougherty wrote:
> >
> > > I'm sorry to report it, but this one isn't fixed. For example, consider
> > > test t/src_hash_6. If I compile and run it manually, I g
On Mon, 18 Jun 2007, chromatic via RT wrote:
> On Monday 18 June 2007 09:54:01 Andy Dougherty wrote:
>
> > I'm sorry to report it, but this one isn't fixed. For example, consider
> > test t/src_hash_6. If I compile and run it manually, I get
> >
> > $ t/src/hash_6
> > 42
> > Segment
On Monday 18 June 2007 09:54:01 Andy Dougherty wrote:
> I'm sorry to report it, but this one isn't fixed. For example, consider
> test t/src_hash_6. If I compile and run it manually, I get
>
> $ t/src/hash_6
> 42
> Segmentation Fault(coredump)
>
> But if I run it via the test harness
Andy Dougherty wrote:
I think the exit code stuff has been changed (this test used to get
reported as failing) but the $builder->diag weirdness is unchanged.
Okay, thanks! We'll work on it some more for the next release.
Allison
I'm sorry to report it, but this one isn't fixed. For example, consider
test t/src_hash_6. If I compile and run it manually, I get
$ t/src/hash_6
42
Segmentation Fault(coredump)
But if I run it via the test harness, I get
$ perl5.8 -Ilib t/src/hash.t
1..11
