Confirmed users
1,351
edits
ReleaseEngineering/TryServer: Difference between revisions
update definition of long, due to cache invalidation
m (→Running a subset of builds/test/talos available to Try: https://bitbucket.org/sfink/trychooser) |
(update definition of long, due to cache invalidation) |
||
| Line 165: | Line 165: | ||
<div id="long_try_push"></div> | <div id="long_try_push"></div> | ||
=== Pushes to try take a very long time === | === Pushes to try take a very long time === | ||
If you're experiencing excessive wait times (> | Note: if a fellow developer cancelled their try push, they have saddled you with the cost of rebuilding the cache. (See [http://dtor.com/halfire/2014/07/02/2014_06_try_server_update.html#caching caching] details.) | ||
If you're experiencing excessive wait times (> 45min) 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. | |||
=== Waiting for Lock === | === Waiting for Lock === | ||