search

google / trace-viewer

https://github.com/catapult-project/catapult/tree/master/tracing#readme
487 stars 84 forks source link

Lets add a trace to test_data/ called rail_example.json #1113

Closed natduca closed 9 years ago

natduca commented 9 years ago

Right now there is no trace in test_data that has enough to show off the rail side panel etc. You have to get measurmt traces, or scroll thorugh the big test data list to find something to use the rail score side panel.

Can we copy a canonical trace from measurmt to test_data? @yuhao @benshayden can one of you drive?

@philippebeaudoin fyi

benshayden commented 9 years ago

sfgate.json has a bunch of Responses and Idles. Does that suffice?

natduca commented 9 years ago

Sorry hehe, not so easy.

The original request was for a file called rail_example. The expectation is we have a canonical file that we use to demonstrate rail, that we tell people to go in order to debug/etc the best that we've got.

We can copy sfgate if you really want, but that file is a half year old so it doesn't contain any of our fresh trace points.

Again, in keeping with the role this file is supposed to fill, we want to keep it semi live while rail is in flux. For insance, when yuhao lands flow events v2, we'd want to update the canonical trace...

yuhao commented 9 years ago

The Flow API v2 is landed (#1079). The roadblock is that PostTask does not always use unique ID for each flow (#1161). Once that's sorted out, we can collect "canonical" traces that all other people can use.

catapult-bot commented 9 years ago

Migrated to https://github.com/catapult-project/catapult/issues/1113