Retry rolling crates that have been missed by earlier attempts.

Problem description
===================

The `create_update_cl.py` tries to generate small, incremental update
CLs.  To do this, it tries to update one create at a time (in an order
based on the size of the crate's update).  Sometimes this produces an
empty diff - e.g. when the crate cannot be updated without first (or
also) updating its dependencies.  Such failed update attempts will not
produce an update CL.

In most the skipped crate will be covered when processing other, related
crates (e.g. usually updating `cxx` also updates `cxxbridge-flags` and
`cxxbridge-macro`).  But before this CL, the skipped crate will just be
ignored - e.g. sometimes `skrifa` cannot be rolled without first
updating `font-types` and `read-fonts` but updating those other 2 crates
doesn't cover `skrifa`.


Changes in this CL
==================

After this CL, the `create_update_cl.py` script will retry updating
crates that haven't been covered by the initial pass through
`todo_crate_ids`.

I've manually tested that this would cover `skrifa` when starting from
`735e580f7914ba6f5ddaebe9702ecde86dcc79f0^`:

```
** Retrying 1 crates.
Updating skrifa@0.19.2 to a newer version...
  Running `gnrt update skrifa@0.19.2` ...
  Running `git mv <old dir> <new dir>` (for better diff)...
  Running `gnrt vendor`...
  Running `gnrt gen`...
```

Bug: None
Change-Id: I4a231ca730060c882bb746b68b18f0bebb5f0a87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5601970
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Ɓukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1311334}
1 file changed
tree: 92414a41f0b7204851fbf5e697dbbd72cc3b2194
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.