Looks like these bots were transitioned to pinpoint? Dave or Simon, can you take a look?

Yeah, we should be able to get this back relatively easily, I think. Dashboard already communicates with Pinpoint, so we can kick off a perf try job instead of a bisect.

The trace url is in the chartjson output, so we just need to surface that in the UI.

The following revision refers to this bug:
  https://chromium.googlesource.com/catapult/+/b9dc069a4752d711a475b196fec927dc749efd20

commit b9dc069a4752d711a475b196fec927dc749efd20
Author: Simon <simonhatch@chromium.org>
Date: Thu Sep 28 17:41:30 2017

Dashboard - Add pinpoint-perf-job-dialog for perf try jobs.

Dashboard initiates perf try jobs when you hit "request debug trace"
via the chart tooltip. This adds a Pinpoint version of the trace
dialog that routes the request to Pinpoint. Basically cloned the
trace-form dialog into pinpoint-perf-job-dialog, and changed the
internals to communicate with the /pinpoint endpoint. Should look
and act exactly the same, with the exception that it will say
"Send to Pinpoint".

Bug:  chromium:768530 
Change-Id: I65d91824a1f73436460ee39e68ce54946d2b279b
Reviewed-on: https://chromium-review.googlesource.com/688826
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Simon Hatch <simonhatch@chromium.org>

[add] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/static/pinpoint.html
[modify] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/dispatcher.py
[modify] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/pinpoint_request_test.py
[modify] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/elements/pinpoint-job-dialog.html
[modify] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/elements/trace-button.html
[modify] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/elements/bisect-button.html
[modify] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/pinpoint_request.py
[add] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/elements/pinpoint-perf-job-dialog-test.html
[add] https://crrev.com/b9dc069a4752d711a475b196fec927dc749efd20/dashboard/dashboard/elements/pinpoint-perf-job-dialog.html

Next steps to finish this off are to support the extra params on Pinpoint's side, and surface the trace links.

 Issue 774947  has been merged into this issue.

All the traces are surfaced after https://github.com/catapult-project/catapult/issues/4048, so this should be fixed.

I just tried to request a debug trace for the regression below, yet can't see whether a try job was kicked off for that - or how to retrieve the try job link. Is that expected?

https://chromeperf.appspot.com/group_report?bug_id=771292

Just noticed that the request try job box says "Only telemetry is supported at the moment." when I open it again after clicking "Send to Pinpoint".

Reopening :)

Ah, that would be a different bug then. Looks like the dialog should wait around for the result of submitting the job from the backend. I've just filed https://github.com/catapult-project/catapult/issues/4075 for that issue.

This isn't a Pinpoint specific limitation, we can only configure the trace categories for telemetry tests and this isn't a telemetry test.

I see, so there's no way of getting a trace out of this particular benchmark in any case? Feel free to close this then.

I could be wrong but I don't think those binaries support getting a trace out, no.