|
|
Chromium Code Reviews|
Created:
4 years, 1 month ago by alancutter (OOO until 2018) Modified:
4 years ago CC:
chromium-reviews, telemetry-reviews_chromium.org, eyaich1 Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMake generate_perf_json.py work regardless of starting working directory
This patch changes generate_perf_json.py such that you are not required
to cd into tools/perf to be able to run it.
BUG=667435
Committed: https://crrev.com/83e8ca3114f774182150be1bd2e4d85fd0b2c7ec
Cr-Commit-Position: refs/heads/master@{#434166}
Patch Set 1 #Patch Set 2 : Simplify #Messages
Total messages: 22 (10 generated)
alancutter@chromium.org changed reviewers: + dtu@chromium.org
Description was changed from ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. ========== to ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. ==========
sullivan@chromium.org changed reviewers: + eyaich@chromium.org
lgtm thanks for doing that!
On 2016/11/21 13:12:13, eyaich1 wrote: > lgtm > > thanks for doing that! (dtu is OOO so it is fine to submit w/just eyaich's review)
Description was changed from ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. ========== to ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. BUG=667435 ==========
The CQ bit was checked by alancutter@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
On 2016/11/21 at 22:33:03, commit-bot wrote: > Try jobs failed on following builders: > chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) Looks like eyaich needs OWNERS for this file.
The CQ bit was checked by eyaich@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 20001, "attempt_start_ts": 1479909218115310,
"parent_rev": "2726c7828636a4eb2b73a76d7a84673964bb3681", "commit_rev":
"2271bdf1d2784e8cddd5526b9787ff3452b67a44"}
Message was sent while issue was closed.
Description was changed from ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. BUG=667435 ========== to ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. BUG=667435 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. BUG=667435 ========== to ========== Make generate_perf_json.py work regardless of starting working directory This patch changes generate_perf_json.py such that you are not required to cd into tools/perf to be able to run it. BUG=667435 Committed: https://crrev.com/83e8ca3114f774182150be1bd2e4d85fd0b2c7ec Cr-Commit-Position: refs/heads/master@{#434166} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/83e8ca3114f774182150be1bd2e4d85fd0b2c7ec Cr-Commit-Position: refs/heads/master@{#434166}
Message was sent while issue was closed.
Looks kind of hacky. The goal is to be agnostic to cwd and the fix is to
introduce cwd logic into the script?
I think the right fix would be to modify line 558.
with open('desktop_benchmark_avg_times.json') as f:
timing_file_path = os.path.join(os.path.dirname(os.path.abspath(__file__)),
'desktop_benchmark_avg_times.json')
with open(timing_file_path) as f:
Message was sent while issue was closed.
On 2016/12/01 at 01:43:18, dtu wrote:
> Looks kind of hacky. The goal is to be agnostic to cwd and the fix is to
introduce cwd logic into the script?
>
> I think the right fix would be to modify line 558.
> with open('desktop_benchmark_avg_times.json') as f:
>
> timing_file_path = os.path.join(os.path.dirname(os.path.abspath(__file__)),
'desktop_benchmark_avg_times.json')
> with open(timing_file_path) as f:
WDTY of having a src_dir() function instead?
Message was sent while issue was closed.
On 2016/12/01 02:31:25, alancutter wrote:
> On 2016/12/01 at 01:43:18, dtu wrote:
> > Looks kind of hacky. The goal is to be agnostic to cwd and the fix is to
> introduce cwd logic into the script?
> >
> > I think the right fix would be to modify line 558.
> > with open('desktop_benchmark_avg_times.json') as f:
> >
> > timing_file_path = os.path.join(os.path.dirname(os.path.abspath(__file__)),
> 'desktop_benchmark_avg_times.json')
> > with open(timing_file_path) as f:
>
> WDTY of having a src_dir() function instead?
Sounds good :)
|
