Telemetry: run_benchmark scheduler.tough_scheduling_cases "WARNING:root:WPR archive missing" |
||||
Issue descriptionWhen I run: tools/perf/run_benchmark run --browser=android-chromium scheduler.tough_scheduling_cases I see the following error in the output: WARNING:root:WPR archive missing: /home/bokan/chrome/src/tools/perf/page_sets/data/tough_scheduling_cases_001.wpr I see that I don't have any wpr files in the page_sets/data directory. The test appears to continue running correctly anyway. Other page sets appear to get the .wpr just fine so perhaps this is just an issue with this one page set and not needing the warning.
,
Oct 3 2016
,
Oct 3 2016
So yes, at this point the warning is not needed. All the page sets are local here so there is no wpr file in cloud storage. The page_sets/data/tough_scheduling_cases_001.wpr doesn't ever get created because this only happens when there is a non-local story. Therefore the page_sets/data/touch_scheduling_cases.json is no longer needed can be removed along with the references in tough_scheduling_cases.py. Since we don't ever try to download, archive_info doesn't actually use the archive_data_file parameter and so it can be safely set to None or not set at all. If you remove these references in tough_scheduling_cases.py this warning will go away.
,
Oct 3 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/eefd038db01368d7f8909141ca38aa07c28d7b61 commit eefd038db01368d7f8909141ca38aa07c28d7b61 Author: scottmg <scottmg@chromium.org> Date: Mon Oct 03 21:50:23 2016 PlzNav: further flaky test filtering in Debug for browser_tests Should have filtered all of BookmarkBubbleSignInDelegateTest per bug 652402 . TBR=jam@chromium.org BUG= 504347 ,652342, 652402 Review-Url: https://codereview.chromium.org/2390843002 Cr-Commit-Position: refs/heads/master@{#422548} [modify] https://crrev.com/eefd038db01368d7f8909141ca38aa07c28d7b61/testing/buildbot/filters/browser-side-navigation.linux.browser_tests.filter
,
Oct 4 2016
Sorry, wrong bug tag for #4. Should have been 652324.
,
Jan 16
,
Jan 16
|
||||
►
Sign in to add a comment |
||||
Comment 1 by nedngu...@google.com
, Oct 3 2016