Updates:
Cc:
d...@chromium.org
Comment #12 on issue 345853 by
dpr...@chromium.org: Create a
Sheesh, sorry for the long delay on this ...
I'm finally at the point where I'm ready and able to start wiring the repos
together. Basically the way things are going to work is as follows:
1) We'll identify subtrees in google3 that will contain page sets,
measurements, and other telemetry-related things. As part of this, for now,
we'll need to identify which tests specifically need to be recorded and
uploaded to cloud storage.
2) We'll clone those over into directories in the new perf-internal chrome
repo. At the moment we will need create a few __init__.py files on the fly
to make the telemetry scripts work, but that can be easily fixed once we
get a better sense that we're happy with the directory structures and
mappings.
3) That perf-internal repo will be pulled in via DEPS entries in
src-internal/DEPS and mapped onto src/tools/perf/internal , where chrome
devs will be able to run the tests just like the public ones.
Once this is all working manually, I'd suggest that this particular bug /
task is complete. We can and should file other bugs to document other tasks
in the system, like updating recordings, updating measurements, adding try
jobs, etc.