Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-05-11 Thread Karl Williamson 

On 05/11/2018 12:29 AM, Yaroslav Kuzmin wrote:

Sorry , a lot of other work.

I  try running bisect.pl script
But bisect.pl script finds not the correct configuration settings
Not a valid compile gcc .

If I try manual running
./Configure -ds -Dusedevel -Dusedl
All correct


We don't understand why the below is getting gcc.  But you should be 
able to avoid this by adding -Dcc=xlc to the bisect command line (or 
whatever compiler you're using)


(11:22) RS12 : PDKUZM | ~/ussport/perl/perl-git
:> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit 
(uc("\x{587}") ne "\x{535}\x{552}");'

We are not bisecting.
HEAD is now at 716a866437... Fix locale failures introduced 5 hours ago
Can't exec "ccache": EDC5129I No such file or directory. at 
/tmp/YlJeWxnMCk line 886.

(I see you are using the Korn shell.  Some ksh's blow up on Configure,
mainly on older exotic systems.  If yours does, try the Bourne shell 
instead.)

First let's make sure your kit is complete.  Checking...
Locating common programs...
Checking compatibility between /bin/echo and builtin echo (if any)...
Symbolic links are supported.
Checking how to test for symbolic links...
Your builtin 'test -h' may be broken.
Trying external '/bin/test -h'.
You can test for symbolic links with '/bin/test -h'.
Checking for cross-compile
No targethost for running compiler tests against defined, running locally
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
aix   esix4 lynxossco_2_3_3
aix_3 fps   midnightbsd   sco_2_3_4
aix_4 freebsd   mips  solaris_2
altos486  freemint  mirbsdstellar
amigaos   gnu   mpc   sunos_4_0
atheosgnukfreebsd   ncr_tower sunos_4_1
aux_3 gnuknetbsdnetbsdsuper-ux
bitriggreenhillsnewsos4   svr4
bsdos haiku nonstopux svr5
catamount hpux  openbsd   ti1500
convexos  i386  opus  ultrix_4
cxux  interix   os2   umips
cygwinirix_4os390 unicos
darwinirix_5os400 unicosmk
dcosx irix_6posix-bc  unisysdynix
dec_osf   irix_6_0  qnx   utekv
dos_djgpp irix_6_1  riscosuwin
dragonfly isc   sco   vos
dynix isc_2 sco_2_3_0
dynixptx  linux-android sco_2_3_1
epix  linux sco_2_3_2
Which of these apply, if any? [os390]
Operating system name? [os390]
Operating system version? [25.00]
Installation prefix to use? (~name ok) [/usr/local]
AFS does not seem to be running...
What installation prefix should I use for installing files? (~name ok)
[/usr/local]
Getting the current patchlevel...
Build a threading Perl? [n]
Build Perl for multiplicity? [n]
Use which C compiler? [cc]
FSUM3007 -l is not a valid option.
Uh-oh, the C compiler 'cc' doesn't seem to be working.
gcc: ./trygcc 25: .: ./Configure 4553: FSUM7351 not found
FSUM3007 -l is not a valid option.
Uh-oh, the C compiler 'cc' doesn't seem to be working.
You need to find a working C compiler.
Either (purchase and) install the C compiler supplied by your OS vendor,
or for a free C compiler try http://gcc.gnu.org/
I cannot continue any further, aborting.
HEAD is now at 716a866437 Fix locale failures introduced 5 hours ago
skipping - could not build config.sh at /tmp/YlJeWxnMCk line 1241.
Runner returned 32000 for end revision, which is a skip at 
Porting/bisect.pl line 234.

That took 20 seconds.


В Ср., 18/04/2018 в 20:08 -0600, Karl Williamson пишет:

On 04/17/2018 01:11 AM, Yaroslav Kuzmin wrote:
Yes . I can actually reasonably bisect. Using the git for z/OS 



Ok.  I have it set up in the branch

smoke-me/khw-yaroslav

That branch is different from blead because it changes the history so
that things that cause EBCDIC not to compile were fixed up.  Otherwise
the bisect would keep finding compilation errors, and not work properly.

To run the bisection do something like


git clone ... bisect
cd bisect
git checkout smoke-me/khw-yaroslav
/path/to/a/functioning/perl/Porting/bisect.pl --start 3b6c52ce7d --end
716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");'

This tool has never been run AFAIK on an EBCDIC machine.  Let's cross
our fingers that it works.  If it works, after some length of time, it
will print a result.  To watch its progress, I pipe it to tee.

above-command | tee ../bisect.out

And then in another window, I do this

tail -f bisect.out | grep steps

I don't know how much of that will work on z/OS.

It can be tricky (at least for me) to get the command exactly right.  I
tested the above-command on my

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-05-11 Thread Yaroslav Kuzmin 
Sorry , a lot of other work.

I  try running bisect.pl script
But bisect.pl script finds not the correct configuration settings
Not a valid compile gcc .

If I try manual running
./Configure -ds -Dusedevel -Dusedl
All correct

(11:22) RS12 : PDKUZM | ~/ussport/perl/perl-git
:> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit 
(uc("\x{587}") ne "\x{535}\x{552}");'
We are not bisecting.
HEAD is now at 716a866437... Fix locale failures introduced 5 hours ago
Can't exec "ccache": EDC5129I No such file or directory. at /tmp/YlJeWxnMCk 
line 886.
(I see you are using the Korn shell.  Some ksh's blow up on Configure,
mainly on older exotic systems.  If yours does, try the Bourne shell instead.)
First let's make sure your kit is complete.  Checking...
Locating common programs...
Checking compatibility between /bin/echo and builtin echo (if any)...
Symbolic links are supported.
Checking how to test for symbolic links...
Your builtin 'test -h' may be broken.
Trying external '/bin/test -h'.
You can test for symbolic links with '/bin/test -h'.
Checking for cross-compile
No targethost for running compiler tests against defined, running locally
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
aix   esix4 lynxossco_2_3_3
aix_3 fps   midnightbsd   sco_2_3_4
aix_4 freebsd   mips  solaris_2
altos486  freemint  mirbsdstellar
amigaos   gnu   mpc   sunos_4_0
atheosgnukfreebsd   ncr_tower sunos_4_1
aux_3 gnuknetbsdnetbsdsuper-ux
bitriggreenhillsnewsos4   svr4
bsdos haiku nonstopux svr5
catamount hpux  openbsd   ti1500
convexos  i386  opus  ultrix_4
cxux  interix   os2   umips
cygwinirix_4os390 unicos
darwinirix_5os400 unicosmk
dcosx irix_6posix-bc  unisysdynix
dec_osf   irix_6_0  qnx   utekv
dos_djgpp irix_6_1  riscosuwin
dragonfly isc   sco   vos
dynix isc_2 sco_2_3_0
dynixptx  linux-android sco_2_3_1
epix  linux sco_2_3_2
Which of these apply, if any? [os390]
Operating system name? [os390]
Operating system version? [25.00]
Installation prefix to use? (~name ok) [/usr/local]
AFS does not seem to be running...
What installation prefix should I use for installing files? (~name ok)
[/usr/local]
Getting the current patchlevel...
Build a threading Perl? [n]
Build Perl for multiplicity? [n]
Use which C compiler? [cc]
FSUM3007 -l is not a valid option.
Uh-oh, the C compiler 'cc' doesn't seem to be working.
gcc: ./trygcc 25: .: ./Configure 4553: FSUM7351 not found
FSUM3007 -l is not a valid option.
Uh-oh, the C compiler 'cc' doesn't seem to be working.
You need to find a working C compiler.
Either (purchase and) install the C compiler supplied by your OS vendor,
or for a free C compiler try http://gcc.gnu.org/
I cannot continue any further, aborting.
HEAD is now at 716a866437 Fix locale failures introduced 5 hours ago
skipping - could not build config.sh at /tmp/YlJeWxnMCk line 1241.
Runner returned 32000 for end revision, which is a skip at Porting/bisect.pl 
line 234.
That took 20 seconds.


В Ср., 18/04/2018 в 20:08 -0600, Karl Williamson пишет:

On 04/17/2018 01:11 AM, Yaroslav Kuzmin wrote:


Yes . I can actually reasonably bisect. Using the git for z/OS




Ok.  I have it set up in the branch

smoke-me/khw-yaroslav

That branch is different from blead because it changes the history so
that things that cause EBCDIC not to compile were fixed up.  Otherwise
the bisect would keep finding compilation errors, and not work properly.

To run the bisection do something like


git clone ... bisect
cd bisect
git checkout smoke-me/khw-yaroslav
/path/to/a/functioning/perl/Porting/bisect.pl --start 3b6c52ce7d --end
716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");'

This tool has never been run AFAIK on an EBCDIC machine.  Let's cross
our fingers that it works.  If it works, after some length of time, it
will print a result.  To watch its progress, I pipe it to tee.

above-command | tee ../bisect.out

And then in another window, I do this

tail -f bisect.out | grep steps

I don't know how much of that will work on z/OS.

It can be tricky (at least for me) to get the command exactly right.  I
tested the above-command on my machine (but I don't have the bug).  If I
screwed up and it says the end commit works, you can add the

--expect-fail

parameter.  Or you can play around until it works.  The file with the
tool contains its pod

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-25 Thread Yaroslav Kuzmin 


В Ср., 25/04/2018 в 12:51 +0100, Dave Mitchell пишет:

On Wed, Apr 25, 2018 at 11:31:13AM +, Yaroslav Kuzmin wrote:


So . I try running bisect.pl

(16:23) RS12 : PDKUZM | ~/ussport/perl/perl-git
:> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit 
(uc("\x{587}") ne "\x{535}\x{552}");'
This checkout is not clean, found file(s):
.gitattributes
1 modified, untracked, or other file(s)
These files may not show in git status as they may be ignored.
Can't run a bisect using a dirty directory containing Porting/bisect-runner.pl.
That took 1 seconds.

I can not  remove this file. This file is very important for the system z/OS



Can't you just move .gitattributes to $GIT_DIR/info/attributes
(or whatever the z/OS equivalent is)?



 Thanks.

Забыл совсем


https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-scm.com%2Fdocs%2Fgitattributes=02%7C01%7Cykuzmin%40rocketsoftware.com%7C956d7be2b8914414232e08d5aaa2f0ec%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636602539176143282=nofEe1YEBsuOMupbeO%2FFIp74XHmnWUYwIU39xyGKAmQ%3D=0




Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-25 Thread Dave Mitchell 
On Wed, Apr 25, 2018 at 11:31:13AM +, Yaroslav Kuzmin wrote:
> So . I try running bisect.pl
> 
> (16:23) RS12 : PDKUZM | ~/ussport/perl/perl-git
> :> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit 
> (uc("\x{587}") ne "\x{535}\x{552}");'
> This checkout is not clean, found file(s):
> .gitattributes
> 1 modified, untracked, or other file(s)
> These files may not show in git status as they may be ignored.
> Can't run a bisect using a dirty directory containing 
> Porting/bisect-runner.pl.
> That took 1 seconds.
> 
> I can not  remove this file. This file is very important for the system z/OS

Can't you just move .gitattributes to $GIT_DIR/info/attributes
(or whatever the z/OS equivalent is)?

https://git-scm.com/docs/gitattributes

-- 
"You may not work around any technical limitations in the software"
-- Windows Vista license

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-25 Thread Michiel Beijen 
Hi,

On Wed, Apr 25, 2018 at 1:31 PM, Yaroslav Kuzmin  wrote:

> So . I try running bisect.pl
>
> (16:23) RS12 : PDKUZM | ~/ussport/perl/perl-git
> :> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit
> (uc("\x{587}") ne "\x{535}\x{552}");'
> This checkout is not clean, found file(s):
> .gitattributes
> 1 modified, untracked, or other file(s)
> These files may not show in git status as they may be ignored.
> Can't run a bisect using a dirty directory containing Porting/
> bisect-runner.pl.
> That took 1 seconds.
>
> I can not  remove this file. This file is very important for the system
> z/OS
>

You can create a file ~/.config/git/ignore with contents

.gitattributes

After you create this file, git will no longer see the repository as
'dirty'.
This is basically a configuration file with .gitignore lines which are
valid for all git repositories for your user; also handy to add files here
which are created by your favourite text editor or IDE.

--
Michiel

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-25 Thread Yaroslav Kuzmin 
So . I try running bisect.pl

(16:23) RS12 : PDKUZM | ~/ussport/perl/perl-git
:> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit 
(uc("\x{587}") ne "\x{535}\x{552}");'
This checkout is not clean, found file(s):
.gitattributes
1 modified, untracked, or other file(s)
These files may not show in git status as they may be ignored.
Can't run a bisect using a dirty directory containing Porting/bisect-runner.pl.
That took 1 seconds.

I can not  remove this file. This file is very important for the system z/OS

.gitattributes file contents

.gitattributes git-encoding=ISO8859-1 working-tree-encoding=IBM-1047
* git-encoding=ISO8859-1 working-tree-encoding=IBM-1047
*.ico binary
*.tar binary
*.tbz binary
*.tgz binary
*.uu binary

--Yaroslav


В Ср., 18/04/2018 в 20:08 -0600, Karl Williamson пишет:

On 04/17/2018 01:11 AM, Yaroslav Kuzmin wrote:


Yes . I can actually reasonably bisect. Using the git for z/OS




Ok.  I have it set up in the branch

smoke-me/khw-yaroslav

That branch is different from blead because it changes the history so
that things that cause EBCDIC not to compile were fixed up.  Otherwise
the bisect would keep finding compilation errors, and not work properly.

To run the bisection do something like


git clone ... bisect
cd bisect
git checkout smoke-me/khw-yaroslav
/path/to/a/functioning/perl/Porting/bisect.pl --start 3b6c52ce7d --end
716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");'

This tool has never been run AFAIK on an EBCDIC machine.  Let's cross
our fingers that it works.  If it works, after some length of time, it
will print a result.  To watch its progress, I pipe it to tee.

above-command | tee ../bisect.out

And then in another window, I do this

tail -f bisect.out | grep steps

I don't know how much of that will work on z/OS.

It can be tricky (at least for me) to get the command exactly right.  I
tested the above-command on my machine (but I don't have the bug).  If I
screwed up and it says the end commit works, you can add the

--expect-fail

parameter.  Or you can play around until it works.  The file with the
tool contains its pod



Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-18 Thread Karl Williamson 

On 04/17/2018 01:11 AM, Yaroslav Kuzmin wrote:

Yes . I can actually reasonably bisect. Using the git for z/OS



Ok.  I have it set up in the branch

smoke-me/khw-yaroslav

That branch is different from blead because it changes the history so 
that things that cause EBCDIC not to compile were fixed up.  Otherwise 
the bisect would keep finding compilation errors, and not work properly.


To run the bisection do something like


git clone ... bisect
cd bisect
git checkout smoke-me/khw-yaroslav
/path/to/a/functioning/perl/Porting/bisect.pl --start 3b6c52ce7d --end 
716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");'


This tool has never been run AFAIK on an EBCDIC machine.  Let's cross 
our fingers that it works.  If it works, after some length of time, it 
will print a result.  To watch its progress, I pipe it to tee.


above-command | tee ../bisect.out

And then in another window, I do this

tail -f bisect.out | grep steps

I don't know how much of that will work on z/OS.

It can be tricky (at least for me) to get the command exactly right.  I 
tested the above-command on my machine (but I don't have the bug).  If I 
screwed up and it says the end commit works, you can add the


--expect-fail

parameter.  Or you can play around until it works.  The file with the 
tool contains its pod

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-17 Thread Yaroslav Kuzmin 


В Вт., 17/04/2018 в 00:42 -0600, Karl Williamson пишет:

On 04/17/2018 12:33 AM, Yaroslav Kuzmin wrote:




В Пн., 16/04/2018 в 22:05 -0600, Karl Williamson пишет:


On 04/16/2018 05:28 AM, Yaroslav Kuzmin wrote:


В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:


On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:


Smoke log available at
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D=0
Automated smoke report for branch blead 5.27.11 patch
5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2
hours (average 1 hour) Summary: FAIL(XM)


The easiest way to find this is to run a bisection on the month or
so's commits that could have caused this. Does your machine have
enough throughput that it could do this?


Yes. It can be done Мощность есть, немного ))




Actually, I'm not so sure.  I believe one needs git to do this.  I
looked at the git web site, and couldn't find any evidence that it was
supported on non-ASCII platforms.




So 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fzos-open-source%2Ftools=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cbb916ad8b2fe476ba25108d5a42e5c0d%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595441392497629=%2B%2FY9sd0t5stXFQLHuBgwEIWIS%2BEo8%2BVvov8Rg%2Fsu8Z8%3D=0

But I am build perl in a separate maint-5.24-zos branch.



I don't understand if that means you can or cannot actually reasonably
bisect



Yes . I can actually reasonably bisect. Using the git for z/OS












And that means compiling perl at a given commit that's bad, and then
cleaning the directory, and running it again at the last known good
commit. Then running it yet again at the commit half way between
these two. Then repeating on the half of the original range where it
changed. We have a tool that will automatically do this. You set it
going, and let it run until it finds the offending commit. I haven't
brought this up before, because I thought your hardware was too slow
for this. But this instance would be relatively few commits, so that
it might be feasible. I would furnish you the correct incantation to
get it to work, after having tested it on my machine.


 Rocket Software, Inc. and
subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll
Free Number: +1 855.577.4323 Contact Customer Support:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupport=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201=0r9Pp%2B3pf4ubny%2Fn7cslkZDwY9yXwSsFdj%2BZfhL3d8k%3D=0
Unsubscribe from Marketing Messages/Manage Your Subscription
Preferences -
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferences=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201=E6Kr%2FLKMSn2qgaVK%2B5Ztc27mNePx7%2BUMKUXvryWoRJQ%3D=0
Privacy Policy -
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fcompany%2Flegal%2Fprivacy-policy=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201=CBVES67q0tkvhJFG96yBMk8ckX15R6sNS2IZPAg9eVw%3D=0
 This communication and any
attachments may contain confidential information of Rocket Software,
Inc. All unauthorized use, disclosure or distribution is prohibited.
If you are not the intended recipient, please notify Rocket Software
immediately and destroy all copies of this communication. Thank you.







Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA
02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupport=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cbb916ad8b2fe476ba25108d5a42e5c0d%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595441392497629=oCFFiePKTgHJ744hmHtNQ8bG%2FiZlujdNIqo47GO4xSw%3D=0
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences
- 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferences=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cbb916ad8b2fe476ba25108d5a42e5c0d%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595441392497629=Bb6IJoJpye%2Fj%2FugIYqeST%2Fcwjs%2BWm0aFAtxqatBaCok%3D=0
Privacy Policy -

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-17 Thread Karl Williamson 

On 04/17/2018 12:33 AM, Yaroslav Kuzmin wrote:



В Пн., 16/04/2018 в 22:05 -0600, Karl Williamson пишет:

On 04/16/2018 05:28 AM, Yaroslav Kuzmin wrote:

В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:

On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
Smoke log available at 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D=0 
Automated smoke report for branch blead 5.27.11 patch 
5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad 
RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2 
hours (average 1 hour) Summary: FAIL(XM) 
The easiest way to find this is to run a bisection on the month or 
so's commits that could have caused this. Does your machine have 
enough throughput that it could do this? 
Yes. It can be done Мощность есть, немного )) 



Actually, I'm not so sure.  I believe one needs git to do this.  I
looked at the git web site, and couldn't find any evidence that it was
supported on non-ASCII platforms.



So http://www.rocketsoftware.com/zos-open-source/tools

But I am build perl in a separate maint-5.24-zos branch.


I don't understand if that means you can or cannot actually reasonably 
bisect





And that means compiling perl at a given commit that's bad, and then 
cleaning the directory, and running it again at the last known good 
commit. Then running it yet again at the commit half way between 
these two. Then repeating on the half of the original range where it 
changed. We have a tool that will automatically do this. You set it 
going, and let it run until it finds the offending commit. I haven't 
brought this up before, because I thought your hardware was too slow 
for this. But this instance would be relatively few commits, so that 
it might be feasible. I would furnish you the correct incantation to 
get it to work, after having tested it on my machine. 
 Rocket Software, Inc. and 
subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll 
Free Number: +1 855.577.4323 Contact Customer Support: 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupport=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201=0r9Pp%2B3pf4ubny%2Fn7cslkZDwY9yXwSsFdj%2BZfhL3d8k%3D=0 
Unsubscribe from Marketing Messages/Manage Your Subscription 
Preferences - 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferences=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201=E6Kr%2FLKMSn2qgaVK%2B5Ztc27mNePx7%2BUMKUXvryWoRJQ%3D=0 
Privacy Policy - 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fcompany%2Flegal%2Fprivacy-policy=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201=CBVES67q0tkvhJFG96yBMk8ckX15R6sNS2IZPAg9eVw%3D=0 
 This communication and any 
attachments may contain confidential information of Rocket Software, 
Inc. All unauthorized use, disclosure or distribution is prohibited. 
If you are not the intended recipient, please notify Rocket Software 
immediately and destroy all copies of this communication. Thank you. 





Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 
02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences 
- http://www.rocketsoftware.com/manage-your-email-preferences

Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential 
information of Rocket Software, Inc. All unauthorized use, disclosure or 
distribution is prohibited. If you are not the intended recipient, 
please notify Rocket Software immediately and destroy all copies of this 
communication. Thank you.

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-16 Thread Karl Williamson 

On 04/16/2018 05:28 AM, Yaroslav Kuzmin wrote:



В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:

On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
Smoke log available at 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D=0 
Automated smoke report for branch blead 5.27.11 patch 
5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad 
RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2 
hours (average 1 hour) Summary: FAIL(XM) 



The easiest way to find this is to run a bisection on the month or so's
commits that could have caused this.  Does your machine have enough
throughput that it could do this?


Yes. It can be done
Мощность есть, немного ))


Actually, I'm not so sure.  I believe one needs git to do this.  I 
looked at the git web site, and couldn't find any evidence that it was 
supported on non-ASCII platforms.







And that means compiling perl at a given commit that's bad, and then
cleaning the directory, and running it again at the last known good
commit.  Then running it yet again at the commit half way between these
two.  Then repeating on the half of the original range where it changed.
   We have a tool that will automatically do this.  You set it going, and
let it run until it finds the offending commit.

I haven't brought this up before, because I thought your hardware was
too slow for this.  But this instance would be relatively few commits,
so that it might be feasible.

I would furnish you the correct incantation to get it to work, after
having tested it on my machine.



Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 
02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences 
- http://www.rocketsoftware.com/manage-your-email-preferences

Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential 
information of Rocket Software, Inc. All unauthorized use, disclosure or 
distribution is prohibited. If you are not the intended recipient, 
please notify Rocket Software immediately and destroy all copies of this 
communication. Thank you.

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-16 Thread Yaroslav Kuzmin 


В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:

On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:



Smoke log available at 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D=0

Automated smoke report for branch blead 5.27.11 patch 
5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
RS12: 2964 (2964/)
 onos/390 - 25.00
 using c99 version
 smoketime 2 hours (average 1 hour)

Summary: FAIL(XM)




The easiest way to find this is to run a bisection on the month or so's
commits that could have caused this.  Does your machine have enough
throughput that it could do this?


Yes. It can be done
Мощность есть, немного ))



And that means compiling perl at a given commit that's bad, and then
cleaning the directory, and running it again at the last known good
commit.  Then running it yet again at the commit half way between these
two.  Then repeating on the half of the original range where it changed.
  We have a tool that will automatically do this.  You set it going, and
let it run until it finds the offending commit.

I haven't brought this up before, because I thought your hardware was
too slow for this.  But this instance would be relatively few commits,
so that it might be feasible.

I would furnish you the correct incantation to get it to work, after
having tested it on my machine.



Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-12 Thread Karl Williamson 

On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:


Smoke log available at 
https://drive.google.com/file/d/1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ

Automated smoke report for branch blead 5.27.11 patch 
5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
RS12: 2964 (2964/)
 onos/390 - 25.00
 using c99 version
 smoketime 2 hours (average 1 hour)

Summary: FAIL(XM)



The easiest way to find this is to run a bisection on the month or so's 
commits that could have caused this.  Does your machine have enough 
throughput that it could do this?


And that means compiling perl at a given commit that's bad, and then 
cleaning the directory, and running it again at the last known good 
commit.  Then running it yet again at the commit half way between these 
two.  Then repeating on the half of the original range where it changed. 
 We have a tool that will automatically do this.  You set it going, and 
let it run until it finds the offending commit.


I haven't brought this up before, because I thought your hardware was 
too slow for this.  But this instance would be relatively few commits, 
so that it might be feasible.


I would furnish you the correct incantation to get it to work, after 
having tested it on my machine.

Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)

2018-04-12 Thread Yaroslav Kuzmin 

Smoke log available at 
https://drive.google.com/file/d/1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ

Automated smoke report for branch blead 5.27.11 patch 
5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
RS12: 2964 (2964/)
onos/390 - 25.00
using c99 version
smoketime 2 hours (average 1 hour)

Summary: FAIL(XM)

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.27.10-119-g5f6af817ad  Configuration (common) none
--- -
X X M - -Dusedl
>
> >
> > >
> > > +- PERLIO = perlio -DDEBUGGING
> > +--- PERLIO = stdio  -DDEBUGGING
> +- PERLIO = perlio
+--- PERLIO = stdio


Locally applied patches:
SMOKE5f6af817add6d2df3603e0e94b6eb27ba5fb3970

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/re/pat_re_eval.t... 
.. FAILED at test 133
../t/uni/tr_utf8.t.. 
. FAILED at test 3
../t/op/utfhash.t... 
.. FAILED at test 28
../t/uni/bless.t 
... FAILED--expected 84 tests, 
saw 80
../lib/feature/unicode_strings.t 
... FAILED at test 4097
../t/mro/basic_01_c3_utf8.t. 
 FAILED--expected 4 tests, saw 3
../lib/bytes.t.. 
. FAILED at test 1
../t/mro/isarev_utf8.t.. 
. FAILED at test 1
../lib/Unicode/UCD.t 
... FAILED at test 170
../ext/XS-APItest/t/gv_autoload4.t.. . 
FAILED at test 21
../t/re/uniprops05.t 
... FAILED at test 19
../t/dist/Safe/t/safeutf8.t. 
.. FAILED at test 2
../t/re/regexp_unicode_prop.t... 
.. FAILED at test 94
../t/dist/Carp/t/arg_string.t... 
 FAILED at test 11
../t/dist/Data-Dumper/t/dumper.t 
. FAILED at test 199
../t/re/uniprops06.t 
... FAILED at test 57
../ext/XS-APItest/t/utf16_to_utf8.t.  
FAILED at test 5
../t/dist/Unicode-Normalize/t/partial1.t . 
FAILED at test 2
../ext/XS-APItest/t/handy00.t... 
.. FAILED at test 140763
../t/re/regexp_qr_embed.t... 
.. FAILED at test 1086
../t/mro/next_inanon_utf8.t. 
 FAILED at test 1
../lib/utf8.t... 
.. FAILED at test 15
../t/op/ver.t... 
.. FAILED at test 14
../t/dist/Storable/t/regexp.t... 
 FAILED at test 43
../t/dist/Unicode-Normalize/t/norm.t . 
FAILED at test 18
../t/op/fresh_perl_utf8.t... 
.. FAILED at test 1
../t/op/utf8cache.t. 
 FAILED at test 4
../t/dist/Carp/t/arg_regexp.t... 
 FAILED at test 11
../t/dist/Unicode-Normalize/t/illegal.t. .. 
FAILED at test 2
../t/re/uniprops02.t 
... FAILED at test 1418
../t/re/uniprops10.t 
... FAILED at test 13
../t/dist/Unicode-Normalize/t/fcdc.t . 
FAILED at test 20
../t/uni/lex_utf8.t. 
 FAILED at test 1
../t/re/reg_fold.t.. 
. FAILED at test 4
../t/dist/IO/t/io_utf8argv.t 
. FAILED at test 1
../ext/B/t/b.t..