I can't run perf try jobs |
||||
Issue descriptionI tried running a perf tryjob with the `run_benchmarks tryjob` command, but it it didn't work and a message says that it's deprecated. So I followed the readme instructions to use pinpoint instead. But I enter all the job information such as configuration, gerritt URL, benchmark, and story, and when I hit started, I get a page that says "Job undefined."
,
Jan 16 2018
What arguments did you use?
,
Jan 16 2018
+dtu
,
Jan 16 2018
Thanks. CL: https://chromium-review.googlesource.com/c/chromium/src/+/865945 Configuration: chromium-rel-mac11-air Benchmark: loading.desktop Story: Chosun
,
Jan 16 2018
I finally got a job going: https://pinpoint-dot-chromeperf.appspot.com/job/11a75290840000 It appears the problem is that I wasn't automatically signed into the website based on my cookies, and it doesn't give an error about signing in, it just says 'job undefined.'
,
Jan 17 2018
Hmm, now there's another problem. I can't access the results for my own job, I get a 403 error: https://pinpoint-dot-chromeperf.appspot.com/results2/11a75290840000
,
Jan 17 2018
Weird - I can access that page. Dave to comment.
,
Jan 17 2018
Looks like we hit a soft memory limit with that request. If you try again, are you able to access? File bugs for both your issues: https://github.com/catapult-project/catapult/issues/4164 https://github.com/catapult-project/catapult/issues/4165
,
Jan 17 2018
I'm still getting this error: Error: Forbidden Your client does not have permission to get URL /results2/11a75290840000 from this server. Can anyone access that page? I want to re-submit the GPU sandbox CL but it's important for me to see the perf results first.
,
Jan 17 2018
I was able to access the page and downloaded it, attached. Simon, Dave, is there already a bug on how long the column header for the patch is?
,
Jan 17 2018
Thank you. So is there just an account permissions issue?
,
Jan 17 2018
I just deployed a new version, turns out I had locked off that endpoint to admin users, do you mind trying that?
,
Jan 17 2018
Spoke to kerrnel@ offline, it's working with the most recent deployment, CL fix is up.
,
Jan 18 2018
Going to close this out. There's still an open issue about making it more clear you need to be signed in that's being tracked separately, but I think the rest of the issues are resolved. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kerrnel@chromium.org
, Jan 16 2018