[roll] Roll fuchsia [persistence] Use B-Tree to group tags by time

Refactor Scheduler to use a B-Tree while grouping tags that need to be
fetched in the future. This is meant to be a readability improvement.
While this also improves over the existing O(N^2) solution with
O(N log N), it may not result in better performance for small values of
N due to the constant time for creating a B-Tree.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1247458
Original-Revision: e14555866daf2363f33265d07d6efd5023fa4679
GitOrigin-RevId: 99b04f4c4d0a3849d101c51482c1ca7e3a5be31f
Change-Id: I7ba22b173312e05d8935b8dd27e4b0e0067be474
1 file changed
tree: 345c2df99c86d398403e8590cbc13e0e6506c8d2
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.