[roll] Roll fuchsia [build] Ensure regeneration when regenerator fails

Delete "stamp files" when regenerator.py fails to ensure it is re-run
in the next build after the issue is resolved.

Original-Fixed: 409575539
Test: Add `return 1` after "From this point forward" and run `fx build` twice, observing that the build fails to start both times.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1249709
Original-Revision: 6806385782e2ce24215cd956f12f03285093b7b4
GitOrigin-RevId: 7b99a940a04f44842d874eb88b92ac7fe23411b8
Change-Id: I5d8a85707999f0b648a5b6e32608b5fc277f6027
1 file changed
tree: 643a0ff61b4985dae8c79964f8bfd5b651cb34c6
  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.