Issue metadata
Sign in to add a comment
|
Telemetry randomly dropping story results |
||||||||||||||||||
Issue descriptionIn the past few days, the VR Telemetry tests have started randomly dropping the results from stories. See the tail end of the graph here for an example https://chromeperf.appspot.com/report?sid=9e6a965aad6f99209333625ce2b55db4124f8ed279938c85c4345c31416ea2c4. This is reproducible both locally and on the bot in our lab that runs the automated test. I haven't confirmed yet that this is VR-only, but I don't believe there have been any recent VR metric changes that would be causing this. What happens is that all 10 stories complete successfully (they can be observed running on the device and the benchmark runner reports them as running successfully), but the majority of results get dropped. This is visible in both the above graph and the local results.html page, which only has links to a random subset of traces instead of all 10.
,
Oct 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/6fd9f08dcb0bd39f70bdac8d73aa4e87b789d6e5 commit 6fd9f08dcb0bd39f70bdac8d73aa4e87b789d6e5 Author: bsheedy <bsheedy@chromium.org> Date: Mon Oct 30 17:46:28 2017 Fix WebVR metric randomly not producing histograms Fixes an issue with WebVR metric seemingly randomly not producing histograms. This was caused by us unconditionally using pushSample for a user expectation instead of using pushSample/pushEvent depending on the type. Bug: chromium:779227 Change-Id: Ife7dca54062d4458d5192a770cec6e721987699a Reviewed-on: https://chromium-review.googlesource.com/742686 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by: Ben Hayden <benjhayden@chromium.org> [modify] https://crrev.com/6fd9f08dcb0bd39f70bdac8d73aa4e87b789d6e5/tracing/tracing/importer/user_model_builder_test.html [modify] https://crrev.com/6fd9f08dcb0bd39f70bdac8d73aa4e87b789d6e5/tracing/tracing/importer/find_input_expectations.html
,
Oct 31 2017
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by bsheedy@chromium.org
, Oct 27 2017Owner: bsheedy@chromium.org