Re: Smoke [blead] v5.26.0-462-g6c4ca75d65 FAIL(X) os/390 25.00 (2964/)

On 07/05/2017 01:23 AM, Yaroslav Kuzmin wrote:
> 
> Smoke log available at https://drive.google.com/file/d/0B5PTttxwo7qARWpqQnVaWkZiT3c
> 
> Automated smoke report for branch blead 5.27.2 patch 6c4ca75d655dc560dfacf633c27f31f751e3f615 v5.26.0-462-g6c4ca75d65
> RS12: 2964 (2964/)
>      on        os/390 - 25.00
>      using     c99 version
>      smoketime 7 hours 46 minutes (average 3 hours 53 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.26.0-462-g6c4ca75d65  Configuration (common) none
> ----------- ---------------------------------------------------------
> X X X X     -Dusedl
>>
>>>
>>>>
>>>> +----- PERLIO = perlio -DDEBUGGING
>>> +------- PERLIO = stdio  -DDEBUGGING
>> +--------- PERLIO = perlio
> +----------- PERLIO = stdio
> 
> 
> Locally applied patches:
>      SMOKE6c4ca75d655dc560dfacf633c27f31f751e3f615
> 
> Tests skipped on user request:
>      # One test name on a line
> Failures: (common-args) none
> [stdio] -Dusedl
> Inconsistent test results (between TEST and harness):
>      ../t/op/sprintf2.t...................... ................................................. FAILED at test 1597
>      ../t/re/pat_advanced.t.................. ............................................. FAILED at test 760
>      ../lib/DBM_Filter/t/encode.t............ ....................................... FAILED at test 14
>      ../ext/File-Glob/t/rt131211.t........... ...................................... FAILED at test 1
>      ../t/porting/podcheck.t................. ............................................ FAILED--expected 1437 tests, saw 0
> 
>

Thanks.  I have submitted patches to blead for the sprintf2.t and 
pat_advanced.t test failures.  They were both problems in the test being 
ASCII-specific, and the code is and was correct.

The encode and podcheck failures are left over from 5.25, and I 
concluded then that they were from a bug in Encode.  I have a fix for 
Encode in the pipeline, but it depends on several other dominoes falling 
to get applied.

The rt131211 failure is new, and I have updated the ticket it refers to 
to correspond.

Shortly, I should be pushing a lot of commits dealing with UTF-8 
handling to blead.  I can't imagine that I got the EBCDIC completely 
correct right out of the box, so I suggest waiting until that lands to 
run your next smoke.

We need to get EBCDIC 5.26 downloadable.  I can't remember how exactly. 
I think you furnish us an EBCDIC tarball that someone installs.