Wireshark mailing list archives
Re: odd Windows petri-dish failure
From: Gerald Combs <gerald () wireshark org>
Date: Wed, 8 Jul 2015 14:28:11 -0700
On 7/8/15 1:46 PM, Hadriel Kaplan wrote:
Anyone seen this type of petri-dish failure before, on the Windows petri-dish, and know what it means? Resolving deltas: 71% (3551/4999) Resolving deltas: 72% (3600/4999) error: index-pack died of signal 11 fatal: index-pack failed program finished with exit code 128 elapsedTime=22.854000
It started showing up after the Gerrit 2.10 upgrade. As far as I can tell it's due to a combination of the following: - Slow initial I/O speeds on AWS EC2[1]. - Git on Windows not being particularly fast. - Gerrit 2.10 timing out HTTP connections after 30 seconds. - The "retry" flag in Buildbot's Git step not doing much of anything. Until one of these is fixed we have a build step named "prefetching git to work around Gerrit timeout and Buildbot retry bugs", which should trigger enough I/O reads to work around the timeout and retry issues. Unfortunately it's not guaranteed to work every time. [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-prewarm.html ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- odd Windows petri-dish failure Hadriel Kaplan (Jul 08)
- Re: odd Windows petri-dish failure Gerald Combs (Jul 08)
- Re: odd Windows petri-dish failure Pascal Quantin (Jul 08)
- Re: odd Windows petri-dish failure Guy Harris (Jul 08)
- Re: odd Windows petri-dish failure Gerald Combs (Jul 08)