History suggests these have been in place for a long time, back to an era when
we used split-horizon DNS and DNS service was flaky. We don't see this sort of
error very often anymore.
Now we have docker images that do not have nslookup installed, and this is
causing retries to fail.
The other option is to use `socket.getaddrinfo` here, but that introduces new
failure mode and could prevent retries that would otherwise succeed. The least
failure-prone approach is just to remove the calls.
MozReview-Commit-ID: JDjhYxUrROS
--HG--
extra : rebase_source : 2e29e9ca19343feea9c505622753cbac1d91012e
From version-control-tools revision
0451f128550d8c9dcf83d6628dea5a8030d5cc08. Vendored without
modifications.
This should be a rubber stamp review since the changes to
robustcheckout were already reviewed.
MozReview-Commit-ID: 3J0db7Cja1D
--HG--
extra : rebase_source : 4e36dc83a486841d253cd365ce7a6ceeb50a8ccc
The robustcheckout extension from revision
134574b64ddfa4d7c31977d792761cceca67665a of the version-control-tools
repo is vendored without modifications.
Changes since last time include printing of the Mercurial version and
more robust handling repositories not using modern storage
requirements.
This patch was not explicitly reviewed by glob. But glob reviewed all
the robustcheckout changes since the last vendor. So by the transitive
property of code review...
MozReview-Commit-ID: CejuVVGpaEy
--HG--
extra : rebase_source : d24dd19357c44f50f7605e974d91434bac3c47f8
extra : source : 68cdc2d1184dec80455ba0ea1ebbcab232b8c119
The robustcheckout extension from revision
134574b64ddfa4d7c31977d792761cceca67665a of the version-control-tools
repo is vendored without modifications.
Changes since last time include printing of the Mercurial version and
more robust handling repositories not using modern storage
requirements.
This patch was not explicitly reviewed by glob. But glob reviewed all
the robustcheckout changes since the last vendor. So by the transitive
property of code review...
--HG--
extra : rebase_source : f511876ecc743e6b453118297d327e9a07bb9441
From revision 19db5f4b5b10f639d24e69a4f21e4e80c6e5bbdd of
version-control-tools. Previous revision was
249a47720ddcf896a9f07600c429a1b4492b805e.
Changes include:
* Use new vfs APIs when available (bug 1359959)
* Mark as compatible with Mercurial 4.2 (bug 1361182)
* Retry after SSLError (bug 1354824)
* Mark as compatible with Mercurial 4.3
* Detect and recover from open locks (bug 1297153)
The most significant is the last one. TaskCluster can SIGKILL
`hg`, leading to orphaned transactions and locks. This can lead
to timeouts or use of a corrupt repository in some scenarios.
Those problems should no longer occur.
MozReview-Commit-ID: QAOSLyc0xD
--HG--
extra : rebase_source : c241626a5a59391b80baf34d50e90fc543e636f7
This is from changeset 249a47720ddcf896a9f07600c429a1b4492b805e from
the version-control-tools repo. It contains a fix to restore
compatibility with Mercurial 3.7, which caused mozharness tests
to fail because that test pins Mercurial 3.7.3 in a requirements
file. This is a bug. But getting a modern robustcheckout deployed
is more important than upgrading that test.
File copied verbatim from changeset e0d30b04dac6bcd36b57c711d9c5b1c280f63390
from the version-control-tools repository.
The updated extension now detects and retries after network failures
where it didn't before. This should cut down on the number of
intermittent failures.
MozReview-Commit-ID: 2bFLcGEARTJ
--HG--
extra : rebase_source : ac43b1925713ce33e1d0d835323efc02c30aed74
From changeset de41dae85307ad65523a7dd2e9ae788490860bdc in the
version-control-tools repository. Added without modifications.
This adds automatic retry functionality to hopefully cut down on the
number of intermittent failures related to connectivity problems.
Self reviewing because the extension changes were already peer
reviewed.
MozReview-Commit-ID: 2vMpM2QHExL
--HG--
extra : rebase_source : 82db28bb9751785801c319a4f9c49d24d61d446b
From changeset 3282813aa892f0fc247181a33ce0bde2b751da50 from the
version-control-tools repo. File added without modifications.
Upstream change was peer reviewed.
From changeset 872711d144202b3f95e090a95f45cc1c45831caf from the
version-control-tools repo. File added without modifications.
Upstream change was peer reviewed.
This new version of the schema validates that numeric values are
within an acceptable range (i.e. are not infinite)
MozReview-Commit-ID: 32oT39Bfcwg
--HG--
extra : rebase_source : 78ef5402e47e05f3f4e5a1db7b36e2d365c7b13b
This new version of the schema validates that numeric values are
within an acceptable range (i.e. are not infinite)
MozReview-Commit-ID: 32oT39Bfcwg
--HG--
extra : rebase_source : 78ef5402e47e05f3f4e5a1db7b36e2d365c7b13b
Synchronized with hgext/robustcheckout/__init.py
from https://hg.mozilla.org/hgcustom/version-control-tools at revision
d2140637eaf3f91fefa7c2f44cbaabf4c19faeb3.
MozReview-Commit-ID: 676o5IVE536
--HG--
extra : rebase_source : 8292cceb465d295f50db68ee0e0fdfb6f6797c26
Having the latest schema available seems like a good thing. This is a
direct copy of schemas/performance-artifact.json from
https://github.com/mozilla/treeherder.git at commit
7bed1b22ceb01e3e71536fa1c4ecd14ddc87e803.
MozReview-Commit-ID: JQC4CeW6szM
--HG--
extra : rebase_source : a57d4e93b9334b5c571b05e0ef52f637a45432dd
Currently, only Talos accesses this file. An uncoming commit will add
a non-Talos consumer. Enable all mozharness consumers to access the
file by including it in the mozharness directory (previously it was
part of the Talos test archive).
MozReview-Commit-ID: ADlCj9E5BwC
--HG--
rename : testing/talos/treeherder-schemas/performance-artifact.json => testing/mozharness/external_tools/performance-artifact-schema.json
extra : rebase_source : ce5fcaf700941ce260c97c6daeefa07b4ef5e617
This is a straight import of version-control-tools:hgext/robustcheckout/__init__.py
at d115bc9578dac4ae2694ea93bb9662de9e6b0b67. Code was reviewed in bug 1274095.
Should be a rubber stamp review.
MozReview-Commit-ID: CEXR9uCHBfI
--HG--
extra : rebase_source : c71bf0bc965993183a197e93459826137392d9e7
We no longer use <3.7 in automation. So drop support for <3.2. While I
was here, I also added magic variables to the extension so Mercurial
can react intelligently to version compatibility issues.
MozReview-Commit-ID: 4tAvQljasDR
--HG--
extra : rebase_source : ef2b5070014507533b5c0ec17449d62ba1bedad8
extra : source : 43c18590fcc7bbf7573647c2f225f4a82dd55730
The build/tools repo has a "purgelong" extension that is used to delete
long filenames on Windows. Without this extension, the APIs Mercurial
uses may run into path length issues and `hg purge` will fail.
This commit is a straight import of the purgelong extension
from https://hg.mozilla.org/build/tools minus the shebang line, which
isn't needed.
MozReview-Commit-ID: FIrEeWDf2Dl
--HG--
extra : rebase_source : ce34dc3dbcfbb9463022f3019f167a58cb396ef3
Andrew Halberstadt
Joel Maher
Justin Wood
Dustin J. Mitchell
Gregory Szorc
Geoff Brown
William Lachance
Phil Ringnalda
Carsten "Tomcat" Book
Kim Moir
Aki Sasaki
Armen Zambrano Gasparnian
Jordan Lund