| commit | a1eef9d74ff6a60ddf7f46faa74bda4b5769ef7c | [log] [tgz] |
|---|---|---|
| author | Benjamin Prosnitz <bprosnitz@fuchsia.infra.roller.google.com> | Fri Mar 04 15:11:47 2022 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 04 07:13:22 2022 -0800 |
| tree | 2c4a4d10a14436d9948774b905ed47ad2a199826 | |
| parent | 3371e3be89c5bc8dac054e78da431fb800170e72 [diff] |
[roll] Roll fuchsia [media] Return status from call failure A recent CL Ic56ed1521003f3f382549e157158be0dfcf1fdd3 added an assertion on call failure, which may not be safe because it crashes the process on failure. This CL updates the behavior to return the status. Let me know whether or not this is the correct way to handle a call failure. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/653922 Original-Revision: 4418d67cc2a678cfa6a2af0fff27c7a723a61fa4 GitOrigin-RevId: b642ea4b27675ec8dd64e578586ea361faa798b9 Change-Id: I2c9bf9e3acbff9fdf81e3dff26ea3a6138af4847
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.