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

On 04/16/2018 05:28 AM, Yaroslav Kuzmin wrote:
>=20
>=20
> =D0=92 =D0=A7=D1=82., 12/04/2018 =D0=B2 23:02 -0600, Karl Williamson =D0=
=BF=D0=B8=D1=88=D0=B5=D1=82:
>> On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
>>> Smoke log available at=20
>>> https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdr=
ive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ&data=3D02%7=
C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C7=
9544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608&sdata=3DzXZi=
EaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D&reserved=3D0=20
>>> Automated smoke report for branch blead 5.27.11 patch=20
>>> 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad=20
>>> RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2=20
>>> hours (average 1 hour) Summary: FAIL(XM)=20
>>
>>
>> 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?
>=20
> Yes.=C2=A0It can be done
> =D0=9C=D0=BE=D1=89=D0=BD=D0=BE=D1=81=D1=82=D1=8C =D0=B5=D1=81=D1=82=D1=8C=
, =D0=BD=D0=B5=D0=BC=D0=BD=D0=BE=D0=B3=D0=BE ))

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



>=20
>> 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 thes=
e
>> two.  Then repeating on the half of the original range where it change=
d.
>>    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.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
> Rocket Software, Inc. and subsidiaries =E2=96=A0 77 Fourth Avenue, Walt=
ham MA=20
> 02451 =E2=96=A0 Main Office Toll Free Number: +1 855.577.4323
> Contact Customer Support:=20
> https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
> Unsubscribe from Marketing Messages/Manage Your Subscription Preference=
s=20
> - http://www.rocketsoftware.com/manage-your-email-preferences
> Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-po=
licy
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> This communication and any attachments may contain confidential=20
> information of Rocket Software, Inc. All unauthorized use, disclosure o=
r=20
> distribution is prohibited. If you are not the intended recipient,=20
> please notify Rocket Software immediately and destroy all copies of thi=
s=20
> communication. Thank you.
>=20