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

2017-10-05 Thread Karl Williamson 

On 10/05/2017 12:18 AM, Yaroslav Kuzmin wrote:

The attached file does not have extra debugging info.


Oops.  Sorry.  I attached a version either from a wrong work space or 
had git stashed it before I sent it.  The one attached to this email 
should have the extra debugging.


 Исходное сообщение 
*От*: Karl Williamson >
*Кому*: Yaroslav Kuzmin >, 
perl-mvs@perl.org >, 
perl5-port...@perl.org >
*Копия*: daily-build-repo...@perl.org >
*Тема*: Re: Smoke [blead] v5.26.0-859-g7bd9fb107e FAIL(X) os/390 25.00 
(2964/)

*Дата*: Tue, 3 Oct 2017 22:54:13 -0600

On 10/03/2017 05:44 AM, Yaroslav Kuzmin wrote:
Dump attachment 



Thanks.  Please try the attached Langinfo.t, which has extra debugging
info to see what happens.


(07:44) RS12 : PDKUZM | ~/ussport/perl/perl-build/ext/I18N-Langinfo :> 
../../perl -I../../lib -T t/Langinfo.t 1..38 ok 1 - use 
I18N::Langinfo; ok 2 - calling langinfo() with ABDAY_1 ok 3 - checking 
if the returned string is defined ok 4 - checking if the returned 
string has a positive length ok 5 - calling langinfo() with DAY_1 ok 6 
- checking if the returned string is defined ok 7 - checking if the 
returned string has a positive length ok 8 - calling langinfo() with 
ABMON_1 ok 9 - checking if the returned string is defined ok 10 - 
checking if the returned string has a positive length ok 11 - calling 
langinfo() with MON_1 ok 12 - checking if the returned string is 
defined ok 13 - checking if the returned string has a positive length 
ok 14 - calling langinfo() with RADIXCHAR ok 15 - checking if the 
returned string is defined ok 16 - checking if the returned string has 
a positive length ok 17 - calling langinfo() with AM_STR ok 18 - 
checking if the returned string is defined ok 19 - checking if the 
returned string has a positive length ok 20 - calling langinfo() with 
THOUSEP ok 21 # skip returned string was empty, skipping next two 
tests ok 22 # skip returned string was empty, skipping next two tests 
ok 23 - calling langinfo() with D_T_FMT ok 24 - checking if the 
returned string is defined ok 25 - checking if the returned string has 
a positive length ok 26 - calling langinfo() with D_FMT ok 27 - 
checking if the returned string is defined ok 28 - checking if the 
returned string has a positive length ok 29 - calling langinfo() with 
T_FMT ok 30 - checking if the returned string is defined ok 31 - 
checking if the returned string has a positive length ok 32 - ABDAY_1 
=> 'Sun' ok 33 - ABMON_1 => 'Jan' ok 34 - DAY_1 => 'Sunday' ok 35 - 
MON_1 => 'January' ok 36 - RADIXCHAR => '.' ok 37 - THOUSEP => '' 
CEE3204S The system detected a protection exception (System Completion 
Code=0C4).  From compile unit 
/u/pdkuzm/ussport/perl/perl-build/sv.c at entry point Perl_newSVpv at 
statement 9410 at  compile unit offset +0134 at entry 
offset +0134 at address 214C97FC. Segmentation fault  
Исходное сообщение  *От*: Karl Williamson 
 
> *Кому*: 
Yaroslav Kuzmin  
>, 
perl-mvs@perl.org   
%3e>>, perl5-port...@perl.org 
  
%3e>> *Копия*: 
daily-build-repo...@perl.org  
 
%3e>> *Тема*: Re: Smoke 
[blead] v5.26.0-859-g7bd9fb107e FAIL(X) os/390 25.00 (2964/) *Дата*: 
Tue, 19 Sep 2017 09:24:46 -0600 On 09/12/2017 02:47 AM, Yaroslav 
Kuzmin wrote:
Smoke log available at 
https://drive.google.com/file/d/0B5PTttxwo7qARVAzdGo5SDFFRWs 
Automated smoke report for branch blead 5.27.4 patch 
7bd9fb107eaf8df3da9ce46c89920f8da72c76ab v5.26.0-859-g7bd9fb107e 
The new failure in this report is CEE3204S The system detected a 
protection exception (System Completion Code=0C4). From entry point 
Perl_newSVpv at compile unit offset +00B8 at entry offset 
+00B8 at address 2124CF20.

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

2017-10-05 Thread Yaroslav Kuzmin 
The attached file does not have extra debugging info.


 Исходное сообщение 
От: Karl Williamson 
>
Кому: Yaroslav Kuzmin 
>,
 perl-mvs@perl.org 
>, 
perl5-port...@perl.org 
>
Копия: daily-build-repo...@perl.org 
>
Тема: Re: Smoke [blead] v5.26.0-859-g7bd9fb107e FAIL(X) os/390 25.00 (2964/)
Дата: Tue, 3 Oct 2017 22:54:13 -0600


On 10/03/2017 05:44 AM, Yaroslav Kuzmin wrote:


Dump attachment



Thanks.  Please try the attached Langinfo.t, which has extra debugging
info to see what happens.





(07:44) RS12 : PDKUZM | ~/ussport/perl/perl-build/ext/I18N-Langinfo
:> ../../perl -I../../lib -T t/Langinfo.t
1..38
ok 1 - use I18N::Langinfo;
ok 2 - calling langinfo() with ABDAY_1
ok 3 - checking if the returned string is defined
ok 4 - checking if the returned string has a positive length
ok 5 - calling langinfo() with DAY_1
ok 6 - checking if the returned string is defined
ok 7 - checking if the returned string has a positive length
ok 8 - calling langinfo() with ABMON_1
ok 9 - checking if the returned string is defined
ok 10 - checking if the returned string has a positive length
ok 11 - calling langinfo() with MON_1
ok 12 - checking if the returned string is defined
ok 13 - checking if the returned string has a positive length
ok 14 - calling langinfo() with RADIXCHAR
ok 15 - checking if the returned string is defined
ok 16 - checking if the returned string has a positive length
ok 17 - calling langinfo() with AM_STR
ok 18 - checking if the returned string is defined
ok 19 - checking if the returned string has a positive length
ok 20 - calling langinfo() with THOUSEP
ok 21 # skip returned string was empty, skipping next two tests
ok 22 # skip returned string was empty, skipping next two tests
ok 23 - calling langinfo() with D_T_FMT
ok 24 - checking if the returned string is defined
ok 25 - checking if the returned string has a positive length
ok 26 - calling langinfo() with D_FMT
ok 27 - checking if the returned string is defined
ok 28 - checking if the returned string has a positive length
ok 29 - calling langinfo() with T_FMT
ok 30 - checking if the returned string is defined
ok 31 - checking if the returned string has a positive length
ok 32 - ABDAY_1 => 'Sun'
ok 33 - ABMON_1 => 'Jan'
ok 34 - DAY_1 => 'Sunday'
ok 35 - MON_1 => 'January'
ok 36 - RADIXCHAR => '.'
ok 37 - THOUSEP => ''
CEE3204S The system detected a protection exception (System Completion
Code=0C4).
  From compile unit /u/pdkuzm/ussport/perl/perl-build/sv.c at
entry point Perl_newSVpv at statement 9410 at
  compile unit offset +0134 at entry offset +0134 at
address 214C97FC.
Segmentation fault



 Исходное сообщение 
*От*: Karl Williamson 
>
*Кому*: Yaroslav Kuzmin 

>,
perl-mvs@perl.org 

%3e>>,
perl5-port...@perl.org 

%3e>>
*Копия*: daily-build-repo...@perl.org 

%3e>>
*Тема*: Re: Smoke [blead] v5.26.0-859-g7bd9fb107e FAIL(X) os/390 25.00
(2964/)
*Дата*: Tue, 19 Sep 2017 09:24:46 -0600

On 09/12/2017 02:47 AM, Yaroslav Kuzmin wrote:


Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qARVAzdGo5SDFFRWs Automated
smoke report for branch blead 5.27.4 patch
7bd9fb107eaf8df3da9ce46c89920f8da72c76ab v5.26.0-859-g7bd9fb107e




The new failure in this report is

CEE3204S The system detected a protection exception (System Completion
Code=0C4).
   From entry point Perl_newSVpv at compile unit offset +00B8
at entry offset +00B8 at address 2124CF20.
ext/I18N-Langinfo/t/Langinfo ..
FAILED--expected 38 tests, saw 37


  From looking at the internet on this, this looks like what's called a
segfault in Unix.  I looked at the code and I don't see anything wrong.

Any ideas?