On 04/12/2017 05:58 AM, Yaroslav Kuzmin wrote:
Manual running test with applied patch

Ok, I'll put this fix into 5.27.


(07:55) RS12 : PDKUZM | ~/ussport/perl/perl-build/t :> ../perl -I../lib 
op/fork.t
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28 # skip Can't set ulimit -u on this system:
1..28



-------- Исходное сообщение --------
От: Karl Williamson <pub...@khwilliamson.com>
Кому: Yaroslav Kuzmin <ykuz...@rocketsoftware.com>, perl-mvs@perl.org 
<perl-mvs@perl.org>, perl5-port...@perl.org <perl5-port...@perl.org>
Копия: daily-build-repo...@perl.org <daily-build-repo...@perl.org>
Тема: Re: Smoke [blead] v5.25.11-11-g772973e FAIL(X) os/390 25.00 (2964/)
Дата: Tue, 11 Apr 2017 14:16:39 -0600

On 04/04/2017 06:06 AM, Yaroslav Kuzmin wrote:

Manual running test
Please try running manually with the attached patch applied.  I think
this will silence the output, and get this test working again.


(07:59) RS12 : PDKUZM | ~/ussport/perl/perl-build/t :> ../perl -I../lib 
op/fork.t
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28 # skip Can't set ulimit -u on this system: ulimit: FSUM6241 Unknown option 
"-u"
ulimit: Usage: ulimit [-aSHctdfsnAM] [n]
1..28


the SHELL environment variable has changed somehow on your system.
Yes, I using bash-4.3 , default SHELL


-------- Исходное сообщение --------
От: Karl Williamson <pub...@khwilliamson.com>
Кому: Yaroslav Kuzmin <ykuz...@rocketsoftware.com>, perl-mvs@perl.org 
<perl-mvs@perl.org>, perl5-port...@perl.org <perl5-port...@perl.org>
Копия: daily-build-repo...@perl.org <daily-build-repo...@perl.org>
Тема: Re: Smoke [blead] v5.25.11-11-g772973e FAIL(X) os/390 25.00 (2964/)
Дата: Fri, 24 Mar 2017 12:29:45 -0600

On 03/24/2017 05:39 AM, Yaroslav Kuzmin wrote:



Smoke log available at 
https://drive.google.com/file/d/0B5PTttxwo7qASTFWbU9YbGVncW8
This and the maint branch both are getting new failures for t/op/fork.t
The logs aren't very helpful.  Looking at the code makes me wonder if
the SHELL environment variable has changed somehow on your system.

In any event, it would be helpful to run this test manually.

cd t
./perl -I../lib op/fork.t

and capture STDERR and STDOUT and send them to the list.



Automated smoke report for branch blead 5.26.0 patch 
772973e0724bdb6a9124827cd75fc2db56e5a443 v5.25.11-11-g772973e
RS12: 2964 (2964/)
    on        os/390 - 25.00
    using     c99 version
    smoketime 16 hours 14 minutes (average 8 hours 7 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.25.11-11-g772973e  Configuration (common) none
----------- ---------------------------------------------------------
X X X X     -Dusedl









+----- PERLIO = perlio -DDEBUGGING
+------- PERLIO = stdio  -DDEBUGGING
+--------- PERLIO = perlio
+----------- PERLIO = stdio


Locally applied patches:
    SMOKE772973e0724bdb6a9124827cd75fc2db56e5a443

Tests skipped on user request:
    # One test name on a line
Failures: (common-args) none
[stdio] -Dusedl
[perlio] -DDEBUGGING -Dusedl
Inconsistent test results (between TEST and harness):
    ../t/porting/podcheck.t................. 
............................................ FAILED--expected 1446 tests, saw 0
    ../t/op/fork.t.......................... 
..................................................... FAILED--unexpected output 
at test 28
    ../lib/DBM_Filter/t/encode.t............ 
....................................... FAILED at test 14

[perlio] -Dusedl
Inconsistent test results (between TEST and harness):
    ../lib/DBM_Filter/t/encode.t............ 
....................................... FAILED at test 14
    ../t/op/fork.t.......................... 
..................................................... FAILED--unexpected output 
at test 28
    ../t/porting/podcheck.t................. 
............................................ FAILED--expected 1446 tests, saw 0

[stdio] -DDEBUGGING -Dusedl
Inconsistent test results (between TEST and harness):
    ../t/re/pat_psycho.t.................... 
............................................... FAILED--expected 15 tests, saw 
10
    ../t/re/fold_grind.t.................... 
............................................... FAILED--no leader found
    ../t/op/fork.t.......................... 
..................................................... FAILED--unexpected output 
at test 28
    ../t/porting/podcheck.t................. 
............................................ FAILED--expected 1446 tests, saw 0
    ../t/re/speed.t......................... 
.................................................... FAILED at test 58
    ../lib/DBM_Filter/t/encode.t............ 
....................................... FAILED at test 14

Compiler messages(os390):



--
Report by Test::Smoke v1.6 running on perl 5.22.0
(Reporter v0.052 / Smoker v0.045)

--

Regards,

Yaroslav Kuzmin
Developer C/C++ ,z/OS , Linux
3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia
Tel:  +7.922.2.38.33.38
Email: ykuz...@rocketsoftware.com
Web: www.rocketsoftware.com


================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 877.328.2932
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.

Reply via email to