Re: Smoke [ebcdic] v5.23.7-47-g8d94bf4 PASS os/390 24.00 (2964/)

[email protected] (Karl Williamson) Wed, 24 Feb 2016 19:43:38 -0700
Newsgroups perl.mvs,perl.perl5.porters,perl.daily-build.reports
Message-ID <[email protected]>
On 02/24/2016 04:09 AM, Yaroslav Kuzmin wrote:
>
> Automated smoke report for branch ebcdic 5.23.8 patch 8d94bf4243326c1052dc37b8e37673e83b66cd11 v5.23.7-47-g8d94bf4
> RS12: 2964 (2964/)
>      on        os/390 - 24.00
>      using     c99 version
>      smoketime 6 hours 16 minutes (average 3 hours 8 minutes)
>
> Summary: PASS

This seems to indicate to me that something is wrong in your procedures 
or hardware.  This version shows as passing, and is essentially the same 
version that showed as failing earlier.

The version being tested here is blead up through commit 22bf43d plus 
one additional commit that was not in blead at that time: 8d94bf4.  The 
latter commit fixes a bug in uniprops.t, and nothing else.

But, we already have earlier test results for 22bf43d.  They show the 
uniprops.t failure, but also a bunch of additional ones: 
lib/Net/hostent.t, io/socket.t, dist/IO/t/io_multihomed.t, and 
dist/IO/t/io_sock.t.

These results are given in this 
email:<[email protected]>

My response to it was surprise, as I had thought we had already tested 
beyond that commit, with only the uniprops.t failure:
http://nntp.perl.org/group/perl.perl5.porters/234364
So it look like I was right.

So, why would testing a particular version pass, then fail, then pass 
again.  The only two possibilities I can think of are that somehow your 
state was not getting completely cleaned out between tests, or there was 
a transient hardware or network failure that has since been corrected. 
All those other failing tests look like network issues to me, though I 
haven't checked.  But there was the additional issue that the smoke 
software seemed to be acting funny, showing things as passing overall, 
when they were apparently not.

I don't know what to do now.  The one thing that occurs to me is to try 
current blead, and see if those problems remain gone.

>
> 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.23.7-47-g8d94bf4  Configuration (common) none
> ----------- ---------------------------------------------------------
> O O O O     -Dusedl
>>>> +----- PERLIO = perlio -DDEBUGGING
>>> +------- PERLIO = stdio  -DDEBUGGING
>> +--------- PERLIO = perlio
> +----------- PERLIO = stdio
>
>
> Locally applied patches:
>      SMOKE8d94bf4243326c1052dc37b8e37673e83b66cd11
>
> Tests skipped on user request:
>      # One test name on a line
> 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: [email protected]
> 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 Commercial Email – [email protected]
> Manage Your Subscription Preferences - http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html
> 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.
>