Issue metadata
Sign in to add a comment
|
No data received for cc_perftests from android-nexus6 since 447263 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 13 2017
Here is the revision log where this started happening: http://test-results.appspot.com/revision_range?start=447263&end=447311 This includes weiliangc@'s latest change to cc_perftests here: https://codereview.chromium.org/2657873003 So I highly suspect this is the cause. Assigning to wei for further triage. last good build: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%282%29/builds/3860 first bad build: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%282%29/builds/3861
,
Feb 13 2017
I renamed the tests and add new test in that CL, so the test with the old name is gone. Also the old name doesn't reflect what the test was doing. The old test DelegatedFrame_ManyQuads_100000_100000 is actually doing DelegatedFrame_ManyQuads_1_100000. And a test for actually 100000_100000 will time out. What it looks like is in https://chromeperf.appspot.com/report?sid=efe2d59c6d6c98da881752b1115c0db20ed4c5ddf2ea57d72bfe14faf12f4865, the second graph is reporting same as first graph, so it is changed to third graph.
,
Feb 13 2017
Aha! Thanks for clarification. Marking as Wontfix as this is just a rename. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by majidvp@google.com
, Feb 13 2017