В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:
On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
Smoke log available at
Automated smoke report for branch blead 5.27.11 patch
RS12: 2964 (2964/)
on os/390 - 25.00
using c99 version
smoketime 2 hours (average 1 hour)
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
Мощность есть, немного ))
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:
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences -
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.