|
|
Description[Telemtry] Create a temp file for storing wpr's stdout & stderr.
Previously, webpagereplay stores all the stdout & stder of the wpr subprocess to
a fix log file path location. It then parses the log lines to get replay server
port assignment. When there are multiple telemetry processes running in parallel,
this cause a concurrency problem.
This patch addresses the issue by create a temp location for the log file path.
This is to make sure that different telemetry processes will write & read to different
log files.
BUG=469296
Committed: https://crrev.com/8cf5c3d2dd0406a80e8f2f3130212ee7b78839be
Cr-Commit-Position: refs/heads/master@{#322247}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Address slamm's comment #
Total comments: 2
Patch Set 3 : Move temp log file clean up to the end of StopServer #Messages
Total messages: 25 (12 generated)
nednguyen@google.com changed reviewers: + slamm@chromium.org, zhenw@chromium.org
On 2015/03/24 18:11:38, nednguyen wrote: lgtm
lgtm One thing this does is make the WPR logs unavailable after a run. At least add a TODO to print them to Chrome's log output. https://codereview.chromium.org/1025553008/diff/1/tools/telemetry/telemetry/c... File tools/telemetry/telemetry/core/webpagereplay.py (right): https://codereview.chromium.org/1025553008/diff/1/tools/telemetry/telemetry/c... tools/telemetry/telemetry/core/webpagereplay.py:80: self._tmp_log_file_path = None tmp -> temp to match tempfile and _CreateTempLogFilePath.
https://codereview.chromium.org/1025553008/diff/1/tools/telemetry/telemetry/c... File tools/telemetry/telemetry/core/webpagereplay.py (right): https://codereview.chromium.org/1025553008/diff/1/tools/telemetry/telemetry/c... tools/telemetry/telemetry/core/webpagereplay.py:80: self._tmp_log_file_path = None On 2015/03/24 21:01:47, slamm wrote: > tmp -> temp to match tempfile and _CreateTempLogFilePath. Done.
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1025553008/1
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from zhenw@chromium.org, slamm@chromium.org Link to the patchset: https://codereview.chromium.org/1025553008/#ps20001 (title: "Address slamm's comment")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1025553008/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
https://codereview.chromium.org/1025553008/diff/20001/tools/telemetry/telemet... File tools/telemetry/telemetry/core/webpagereplay.py (right): https://codereview.chromium.org/1025553008/diff/20001/tools/telemetry/telemet... tools/telemetry/telemetry/core/webpagereplay.py:217: self._CleanUpTempLogFilePath() The try job failed because the WPR process is still using the log file. This needs to move to the end of this function.
https://codereview.chromium.org/1025553008/diff/20001/tools/telemetry/telemet... File tools/telemetry/telemetry/core/webpagereplay.py (right): https://codereview.chromium.org/1025553008/diff/20001/tools/telemetry/telemet... tools/telemetry/telemetry/core/webpagereplay.py:217: self._CleanUpTempLogFilePath() On 2015/03/25 19:34:39, slamm wrote: > The try job failed because the WPR process is still using the log file. > This needs to move to the end of this function. Thanks Steve.
The CQ bit was checked by nednguyen@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from zhenw@chromium.org, slamm@chromium.org Link to the patchset: https://codereview.chromium.org/1025553008/#ps40001 (title: "Move log file clean up to the end of StopServer")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1025553008/40001
Patchset #3 (id:40001) has been deleted
The CQ bit was unchecked by nednguyen@google.com
The CQ bit was checked by nednguyen@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from zhenw@chromium.org, slamm@chromium.org Link to the patchset: https://codereview.chromium.org/1025553008/#ps60001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1025553008/60001
Message was sent while issue was closed.
Committed patchset #3 (id:60001)
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/8cf5c3d2dd0406a80e8f2f3130212ee7b78839be Cr-Commit-Position: refs/heads/master@{#322247} |