develooper Front page | perl.mvs | Postings from April 2018

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

Thread Previous | Thread Next
From:
Karl Williamson
Date:
April 17, 2018 04:06
Subject:
Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00(2964/)
Message ID:
ec63814d-5ceb-a16b-5e5d-6780773cd37d@khwilliamson.com
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&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608&sdata=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D&reserved=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.
> 

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About