Swarming: Attach task's processes log to the task as metadata |
|||||||||||
Issue descriptionGoal: Stops having to ssh to a bot to get the logs for a task. Instead, the process specific logs (task_runner.py, run_isolated.py) for a task are stored along the task inside TaskOutput<id=foo.log>. AIs: Bot: - bot_main: after reaping a task, creates a task specific log directory "logs/<task_id>/" and instruct task_runner (and incidentally run_isolated) to use it instead of "logs/". - bot_main: upon task_runner termination, bot_main "amends" a task with the task logs. Server: - Update task/ endpoint group to retrieve named resources. This is also needed for stdout/stderr disambiguation as per issue 732802. Alternative: - Store on the isolate server. It has the advantage of automatic cleanup but enforce close coupling with isolate server, which I prefer not to. Adapted from https://github.com/luci/luci-py/issues/291 ⛆ |
|
|
,
Jun 13 2017
,
Jun 20 2017
,
Jul 12 2017
,
Aug 2 2017
,
Feb 26 2018
,
Today
(21 hours ago)
,
Today
(21 hours ago)
1. Update bot_main.py for the task_runner_stdout.log: https://chromium.googlesource.com/infra/luci/luci-py/+/69654413254983fc60b98cfa0345fa43335536e9/appengine/swarming/swarming_bot/bot_code/bot_main.py#880 2. Pass an explicit --log-file argument 3. Update task_runner to pass --log-file to run_isolated https://chromium.googlesource.com/infra/luci/luci-py/+/69654413254983fc60b98cfa0345fa43335536e9/appengine/swarming/swarming_bot/bot_code/task_runner.py#141
,
Today
(21 hours ago)
|
||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by maruel@google.com
, Jun 13 2017