build103-m4 having issues |
||
Issue descriptionHostname: https://chromium-swarm.appspot.com/bot?id=build103-m4&selected=1&sort_stats=total%3Adesc New bot code is bad: proc exit = -1073741502. stdout: Calling stack: 0 swarming_bot.1.zip\api\bot.py:216:post_error() 1 swarming_bot.1.zip\bot_code\bot_main.py:1241:_bot_restart() 2 swarming_bot.1.zip\bot_code\bot_main.py:1220:_update_bot() 3 swarming_bot.1.zip\bot_code\bot_main.py:1182:_poll_server() 4 swarming_bot.1.zip\bot_code\bot_main.py:1070:_run_bot_inner() 5 swarming_bot.1.zip\bot_code\bot_main.py:966:_run_bot() 6 swarming_bot.1.zip\bot_code\bot_main.py:1351:main() 7 swarming_bot.1.zip\__main__.py:166:CMDstart_bot() 8 swarming_bot.1.zip\__main__.py:252:main() 9 swarming_bot.1.zip\__main__.py:264:<module>() 10 runpy.py:72:_run_code() 11 runpy.py:174:_run_module_as_main()
,
Apr 18 2018
https://chromium-swarm.appspot.com/task?id=3c0c0cfa99d04f10 (run_telemetry_benchmark_as_googletest) permanently hosed the bot.
,
Apr 20 2018
To clarify, the pinpoint task ran a telemetry test that caused the STATUS_DLL_INIT_FAILED issue. The symptom is due to the test killing the Swarming bot console, which then cannot start any child process anymore.
,
Apr 20 2018
I removed the old c:\b\s directory, rebooted the machine and re-bootstrapped the swarming client to un-wedge the machine for now.
,
Apr 23 2018
Thanks! The bot seems to be working now, closing as fixed. |
||
►
Sign in to add a comment |
||
Comment 1 by sergeybe...@chromium.org
, Apr 18 2018Owner: sergeybe...@chromium.org
Status: Assigned (was: Untriaged)