autotest shoud store servod log |
|||||
Issue descriptionOn autotest runs, and especially on repair runs, autotest should store logs from servod. These logs are already present on the labstation under /var/log/servod_XXXX.log so this would only be a matter of storing off the log int the autotest results.
,
May 22 2018
For servov3 it is /var/log/servod_9999.log for newer builds and /var/log/servod.log for older builds (pre-2018/2017?)
,
Jun 1 2018
,
Jun 26 2018
,
Jul 24
Move out of triage queue
,
Jul 24
Issue 851661 has been merged into this issue.
,
Jul 25
,
Jul 25
> Issue 851661 has been merged into this issue. Er... This isn't really a duplicate; the other bug is asking for a different file. However, it might be better to have a single bug asking for various system logs, rather than file one bug per log. That's especially true because there's a common issue that would have to be addressed if we do this: the logs being requested are likely to constitute a fair-sized amount of data, and that data will only get bigger over time, for any labstation that is actually reliable enough to stay running long enough. So, we'd need to make sure that labstation log gathering didn't become an unbounded consumer of bandwidth and storage.
,
Oct 12
Part of 2019 planning. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nsanders@chromium.org
, May 22 2018