Re: Smoke [ebcdic] v5.21.9-306-g6b2c3d7 FAIL(X) os/390 23.00 (2817/)

On 03/19/2015 06:34 AM, Yaroslav Kuzmin wrote:
> Smoke log available at https://drive.google.com/file/d/0B5PTttxwo7qAMHZmcFZic3RGU2c
>
>
> Automated smoke report for branch ebcdic 5.21.10 patch 6b2c3d7cd9f45c0be3a892b77a571dc37e3ccc54 v5.21.9-306-g6b2c3d7
> RS12: 2817 (2817/)
>      on        os/390 - 23.00
>      using     c99 version
>      smoketime 6 hours 58 minutes (average 3 hours 29 minutes)
>
> Summary: FAIL(X)
>
> O = OK  F = Failure(s), extended report at the bottom
> X = Failure(s) under TEST but not under harness
> ? = still running or test results not (yet) available
> Build failures during:       - = unknown or N/A
> c = Configure, m = make, M = make (after miniperl), t = make test-prep
>
> v5.21.9-306-g6b2c3d7  Configuration (common) none
> ----------- ---------------------------------------------------------
> X X X X
> | | | +----- PERLIO = perlio -DDEBUGGING
> | | +------- PERLIO = stdio  -DDEBUGGING
> | +--------- PERLIO = perlio
> +----------- PERLIO = stdio
>
>
> Locally applied patches:
>      SMOKE6b2c3d7cd9f45c0be3a892b77a571dc37e3ccc54
>
> Tests skipped on user request:
>      # One test name on a line
> Failures: (common-args) none
> [stdio/perlio]
> [stdio/perlio] -DDEBUGGING
> Inconsistent test results (between TEST and harness):
>      ../lib/meta_notation.t.................. ............................................. FAILED at test 3
>

The debugging info I added led me straightaway to finding the problem, 
and it was my fault.  And the fix has been pushed to blead.

And the branch you've been testing from has been updated as well.  Now 
it is the same as blead, except for you have the additional Configure 
patch that points to bash instead of /bin/sh.  In other words, blead 
core-Perl now supports z/OS.

If you smoke this branch, we should finally get everything passing.

We're about to enter the period of code freeze until the release of 
v5.22.  Only code changes to things blocking the release are likely to 
go in.  I'll push any significant fixes to your branch to verify that we 
haven't broken anything.

During code freeze, I expect to find some time to work on the cpan 
modules that ship with core and are still failing, starting with Encode.