Actually, removing 900935 the list of blocked bugs. For some reason or another, the HTML files for the Telemetry tests on the internal clank waterfall are at least available at the bottom of the Telemetry standard output. This doesn't seem to be the case for OBBS Telemetry output.

(Even for that file, it took me ~30m of digging in order to find the HTML file, so it'd be really useful still to have an easy way to access the HTML file as a story artifact listed in the json.output file.)

Adding eyaich@ as the likely owner here, given that this seems like it might be related to the OBBS migration.

So I think what is happening here is Ned implemented a feature in telemetry to output logs for each benchmark and include that in the artifacts so there was an easy way to access the logs for individual benchmarks instead of having to load the entire shard which is the results of multiple benchmarks running.

ie we wanted you to click on the "Benchmark Logs" link and lookup your benchmark instead of going to the chrome-swarming* page and loading the entire run.  

That being said, I do remember a design decision when we were talking about the feature (although I can't find the thread/bug atm) that we accepted that these logs only include what is run during the benchmark execution itself. 

Ned do you remember the implementation here and exactly what gets excluded? 

That being said, the trace link is in the larger shard output: 

https://chrome-swarming.appspot.com/task?id=410c830202948f10&refresh=10&show_raw=1

View generated trace files online at https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/long_running_tools_gmail_foreground_2018-11-08_06-50-27_42952.html for story long_running:tools:gmail-foreground

I don't know why your search for cloudstorage didn't show any results, maybe the shard hadn't finished loading yet?

Would it be possible to just add the URL of the uploaded trace file as a test artifact like we do for the uploaded logs?

(And thank you for finding the trace! It looks like after searching, I didn't wait long enough for the search to actually complete.)

#6: yes, I think we can add the URL of the uploaded trace as a test artifact. Though it would require wranggling with the life cycle of the trace a bit. 

I recall the reason we didn't do in the first place is because we have one system of uploading traces to cloud storage [1] that is separate from the system that uploads artifcats to cloud storage [2]. The challenge with merging [1] to [2] has something to do with being able to write the trace URLs to the results format :-/

[1] https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/value/trace.py?rcl=eaddc34b5d484d7a65cfdb2cf8a0373cd2e09025&l=138
[2] https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/results/page_test_results.py?rcl=eaddc34b5d484d7a65cfdb2cf8a0373cd2e09025&l=624

The NextAction date has arrived: 2018-11-19

This might not be too bad.  We could pass state here from one call to another, or save it in the page_test_results:

https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py?l=419