Confirmed users
1,364
edits
ReleaseEngineering/TryServer: Difference between revisions
Jump to navigation
Jump to search
add info on requesting a try reset
(add info on requesting a try reset) |
|||
| Line 146: | Line 146: | ||
== Problem Diagnosis == | == Problem Diagnosis == | ||
=== Can not access try server === | |||
Test your account & configuration | Test your account & configuration | ||
* <code>ssh hg.mozilla.org</code>, response: "No Interactive shells allowed here!" | * <code>ssh hg.mozilla.org</code>, response: "No Interactive shells allowed here!" | ||
* <code>ssh hg.mozilla.org clone invalid_sandbox</code>, response: menu display and interactive prompting. | * <code>ssh hg.mozilla.org clone invalid_sandbox</code>, response: menu display and interactive prompting. | ||
=== Pushes to try take a very long time === | |||
If you're experiencing excessive wait times (> 15min) pushing to try, please file a bug asking IT to reset the try repository using [https://bugzilla.mozilla.org/enter_bug.cgi?comment=please%20schedule%20a%20reset%20of%20the%20try%20repository%20ASAP%20with%20sheriffs%20%26%20releng.&component=WebOps%3A%20Source%20Control&op_sys=All&product=Infrastructure%20%26%20Operations&rep_platform=All&short_desc=Push%20to%20try%20taking%20XXX%20minutes this template] (please include specifics of your experience). They will coordinate with sheriffs and release engineering as needed. | |||
== Buildduty issues == | == Buildduty issues == | ||