| commit | a8f919ba876f04897bdc7fb0e5653647b08fecc6 | [log] [tgz] |
|---|---|---|
| author | Petr Hosek <phosek@fuchsia.infra.roller.google.com> | Mon Feb 06 14:48:03 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 06 06:49:07 2023 -0800 |
| tree | 85e12b40546cb03141a88ed78b980f0806fb5fbd | |
| parent | c138932648c94942e5f6acc0a2be9e9ec4c13eff [diff] |
[roll] Roll infra/recipes Revert "Reland "[testing_requests] Upload files directly from build dir"" This reverts commit 44474dcc5aabf73bb73ffcb051be76a1443d66cd. Reason for revert: This broke Clang toolchain canary builders. Original change's description: > Reland "[testing_requests] Upload files directly from build dir" > > This reverts commit f4200217d722d51344292c5c066bebf09d42f782. > > Reason for revert: fixed by https://crrev.com/c/4027826 > > Original change's description: > > Revert "[testing_requests] Upload files directly from build dir" > > > > This reverts commit 40a36a7a72491ef09d5e5275a91456ba2bf582d4. > > > > Reason for revert: It broke Fuchsia Toolchain Canary builders. > > fxbug.dev/120518 > > > > Original change's description: > > > [testing_requests] Upload files directly from build dir > > > > > > Instead of copying all the dependencies of each shard into a temporary > > > directory and uploading that directory to CAS, upload files directly > > > from the build directory. This eliminates the overhead of copying the > > > shard dependencies, which cuts about 1m15s off the duration of the CQ > > > long pole builder (core.x64-asan). > > > > > > It also means that the paths at which files are accessed on the testing > > > bot correspond directly to the paths at which those files are produced > > > in the build directory (e.g. botanist is now at `./host_x64/botanist` > > > instead of `./botanist`) which is helpful for clarity and consistency. > > > > > > The one downside is that we now need to write the botanist config file > > > and the test manifest into the build directory before uploading, which > > > pollutes the build directory with files not produced by ninja. I don't > > > think this is an issue as long as we give the files shard-specific names > > > to avoid collisions, and clean them up after uploading. testsharder > > > already writes package repository files to the build directory and those > > > don't get cleaned up, so I don't expect these new files to cause any > > > issues. > > > > > > Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/791027 > > > > Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/792922 > > Original-Bug: 120518 > Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/793022 Original-Bug: 120518 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/797425 Original-Revision: e30f85cabd2fa22d95aebd673a0970ca23109b3a GitOrigin-RevId: 2b1be9c730778732b10970b05269798e4958cc76 Change-Id: I6207274d35b47d126e13f14d8eff8b8b22a07353
This repository contains Fuchsia's Global Integration manifest files.
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 via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.