Revert "[Dolphin] Refactor in preparation for query-based predictions."
This reverts commit 6d39702e. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 630682 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzZkMzk3MDJlNzQ4YWUzMzg0MmU1MzlhZmNmNTVlYjI2MjM1ODJkODAM Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/19798 Sample Failed Step: non_single_process_mash_unit_tests Original change's description: > [Dolphin] Refactor in preparation for query-based predictions. > > - Extra methods added to RecurrenceRanker and RecurrencePredictor to accept queries. > > - Storage of targets has been moved from the RecurrenceRanker to individual > RecurrencePredictors. As a result, RecurrencePredictor must now handle targets > renames and removes themselves. Methods for this have been added to their API. > > This is necessary because query-based predictions will require a different data > structure to store target + query than zero-state predictions, which only require > a target. In order to keep the RecurrenceRanker usable for both tasks, choice of > data structure needs to moved into the RecurrencePredictors, where individual > predictors can use what's suitable. > > - The original FrecencyPredictor has been renamed ZeroStateFrecencyPredictor. > > - Some extra tests added. > > Bug: 921444 > Change-Id: I95a6dca135928726c779261ec6b1663b1023bf1f > Reviewed-on: https://chromium-review.googlesource.com/c/1459856 > Reviewed-by: Jia Meng <jiameng@chromium.org> > Commit-Queue: Tony Yeoman <tby@chromium.org> > Cr-Commit-Position: refs/heads/master@{#630682} Change-Id: I9ac4e9efc7abf31d64e30cd9e3f5a1fa55bd9778 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 921444 Reviewed-on: https://chromium-review.googlesource.com/c/1462426 Cr-Commit-Position: refs/heads/master@{#630687}
Showing
Please register or sign in to comment