| commit | 5037130ad1642ec9687247c2ff83065711252f85 | [log] [tgz] |
|---|---|---|
| author | pigweed-integration-roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Sep 21 21:13:10 2021 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 21 21:34:19 2021 +0000 |
| tree | f6607b9f3e7665d4be8a7e9269e50b2df6690244 | |
| parent | 5943b4b261a5f1b7fe1b8c3a2a7bbc57db6e5a47 [diff] |
[roll third_party/pigweed] pw_presubmit: Use log to write subprocess output When PW_PRESUBMIT_DISABLE_SUBPROCESS_CAPTURE is set, use the logging framework to write subprocess output. This way each line has a timestamp so it'll be possible to see if ninja got stuck or if the build was still running when a buildbucket timeout was hit. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/61345 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 054771a4e3d65d5..e485396bb16b735 Roller-URL: https://ci.chromium.org/b/8835446422217541233 Cq-Cl-Tag: roller-builder:pigweed-experimental-roller Cq-Cl-Tag: roller-bid:8835446422217541233 CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia15c23c1092945be8cd6c926d407ba91487c11aa Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/experimental/+/61763 Bot-Commit: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com> Commit-Queue: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
diff --git a/third_party/pigweed b/third_party/pigweed index 054771a..e485396 160000 --- a/third_party/pigweed +++ b/third_party/pigweed
@@ -1 +1 @@ -Subproject commit 054771a4e3d65d5e14772cf97902a1b01f47fed7 +Subproject commit e485396bb16b735b0c6c227fe64e1e0c551143b6