Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Smoke [blead] v5.25.7-50-g4f738c7 FAIL(X) os/390 25.00 (2964/)

1 view
Skip to first unread message

Karl Williamson

unread,
Dec 7, 2016, 1:15:02 AM12/7/16
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
On 12/06/2016 04:26 AM, Yaroslav Kuzmin wrote:
>
> Smoke log at available https://drive.google.com/file/d/0B5PTttxwo7qAdG1UbDdncHNOdG8
>
> Automated smoke report for branch blead 5.25.8 patch 4f738c750ddb40ef82b46158f89572739a8b186a v5.25.7-50-g4f738c7
> RS12: 2964 (2964/)
> on os/390 - 25.00
> using c99 version
> smoketime 5 hours 17 minutes (average 2 hours 38 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.7-50-g4f738c7 Configuration (common) none
> ----------- ---------------------------------------------------------
> X X X X -Dusedl
> | | | +----- PERLIO = perlio -DDEBUGGING
> | | +------- PERLIO = stdio -DDEBUGGING
> | +--------- PERLIO = perlio
> +----------- PERLIO = stdio
>
>
> Locally applied patches:
> SMOKE4f738c750ddb40ef82b46158f89572739a8b186a
>
> Tests skipped on user request:
> # One test name on a line
> Failures: (common-args) none
> [stdio] -Dusedl
> Inconsistent test results (between TEST and harness):
> ../ext/XS-APItest/t/utf8.t.............. ......................................... FAILED at test 157018
> ../t/dist/Net-Ping/t/010_pingecho.t..... .................................. FAILED at test 2
> ../lib/warnings.t....................... .................................................. FAILED at test 519
> ../lib/locale.t......................... .................................................... FAILED at test 408

Thanks. The APItest failures are down from a couple hundred to just 7,
and those 7 are due to an oversight on my part, and there is a fix now
in blead. Blead also contains a fix for the locale.t failure.

I cant figure out why the warnings.t failure is happening. To that end,
attached is a patch to apply to blead to add debugging info to help me.
Compile with -DDEBUGGING, then manually

cd t
./perl -I../lib ../lib/warnings.t

and capture the output and send to me.

I do not know enough to know why the pingecho.t test is failed. This is
a recent addition. It is trying to do a loopback test to 127.0.0.1. Do
you know of any reason this would fail on your system? Maybe it isn't
configured right? If there is such a reason, how could we tell so as to
skip the test?
>
> [perlio] -Dusedl
> Inconsistent test results (between TEST and harness):
> ../ext/XS-APItest/t/utf8.t.............. ......................................... FAILED at test 157018
> ../lib/locale.t......................... .................................................... FAILED at test 408
> ../t/dist/Net-Ping/t/010_pingecho.t..... .................................. FAILED at test 2
> ../lib/warnings.t....................... .................................................. FAILED at test 519
>
> [stdio/perlio] -DDEBUGGING -Dusedl
> Inconsistent test results (between TEST and harness):
> ../lib/locale.t......................... .................................................... FAILED at test 408
> ../lib/warnings.t....................... .................................................. FAILED at test 519
> ../t/dist/Net-Ping/t/010_pingecho.t..... .................................. FAILED at test 2
> ../ext/XS-APItest/t/utf8.t.............. ......................................... FAILED at test 157018
>
> 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: YKu...@rocketsoftware.com
> Web: www.rocketsoftware.com
>
> ================================
> Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ +1 877.328.2932+1 781.577.4321
> 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.
>

0027-utf8.c-Debugging-code-for-Yaroslav.patch

Karl Williamson

unread,
Dec 13, 2016, 7:15:02 PM12/13/16
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
On 12/13/2016 06:42 AM, Yaroslav Kuzmin wrote:
>
>
> -------- Исходное сообщение --------
> От: Karl Williamson <pub...@khwilliamson.com>
> Кому: Yaroslav Kuzmin <yku...@rocketsoftware.com>, perl...@perl.org <perl...@perl.org>, perl5-...@perl.org <perl5-...@perl.org>
> Копия: daily-bui...@perl.org <daily-bui...@perl.org>
> Тема: Re: Smoke [blead] v5.25.7-50-g4f738c7 FAIL(X) os/390 25.00 (2964/)
> Дата: Tue, 6 Dec 2016 23:09:14 -0700
> log available at https://drive.google.com/file/d/0B5PTttxwo7qAZmw1Y0I1N1o1UE0
>
>> and capture the output and send to me.

Thanks. This led me immediately to finding the problem, a missing pair
of parentheses, and it is now fixed in blead.

The new failures look to me to be because of EBCDIC-only bugs in the new
version of Encode, 2.88, recently placed in blead. To be sure, I
modified one of the tests to not use Encode, which it probably shouldn't
have been doing in the first place. This too is in blead.
>
>> I do not know enough to know why the pingecho.t test is failed. This is
>> a recent addition. It is trying to do a loopback test to 127.0.0.1. Do
>> you know of any reason this would fail on your system? Maybe it isn't
>> configured right? If there is such a reason, how could we tell so as to
>> skip the test?
>
> I do not have the rights to run the ping tool.

So, would that explain why it is failing?
0 new messages