chromium.tryserver.win slave state stale |
||||||
Issue descriptionhttps://codereview.chromium.org/1183563003 made it so that slave checkouts ignore master state and use slave state instead. It looks like this isn't working fully reliably. https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang?numbuilds=200 has occasional blocks of "Exception steps exception setup_properties" exceptions, an example is here: https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/147 @@@STEP_CURSOR setup_properties@@@ @@@STEP_STARTED@@@ @@@STEP_CURSOR setup_properties@@@ @@@STEP_LOG_LINE@exception@Traceback (most recent call last):@@@ @@@STEP_LOG_LINE@exception@ File "../../../scripts/slave/annotated_run.py", line 599, in get_recipe_properties@@@ @@@STEP_LOG_LINE@exception@ workdir, mastername, buildername)@@@ @@@STEP_LOG_LINE@exception@ File "../../../scripts/slave/annotated_run.py", line 681, in get_factory_properties_from_disk@@@ @@@STEP_LOG_LINE@exception@ (buildername, mastername))@@@ @@@STEP_LOG_LINE@exception@LookupError: builder "win_clang" not found on in master "tryserver.chromium.win"@@@ @@@STEP_LOG_END@exception@@@ @@@STEP_EXCEPTION@@@ I think I configured the master correctly and restarted it yesterday night, and based on most builds succeeding, I think that's true. It looks like these mostly happen on few slaves: https://build.chromium.org/p/tryserver.chromium.win/buildslaves/vm612-m4 https://build.chromium.org/p/tryserver.chromium.win/buildslaves/vm624-m4 ...oh, it looks like update_scripts fails with "fatal: Unable to create 'E:/b/build/.git/refs/remotes/origin/master.lock': File exists." Maybe the code from https://codereview.chromium.org/1183563003 should print a better error message if the slave checkout is out of date. I'll file a different ticket for getting these two slaves cleaned up, so I suppose this bug isn't super important. Maybe it helps someone googling for this error in the future.
,
Mar 30 2016
(filed bug 599257 for the two slaves failing to update.)
,
Mar 30 2016
,
Apr 27 2016
,
Sep 1 2016
,
Sep 4 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2017
I think it's safe to close this. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dpranke@chromium.org
, Mar 30 2016