[roll] Roll fuchsia [routing] every RoutingError variant has a moniker

In order to preserve UX in scrutiny, every routing error variant should
include a moniker indicating where the routing error happened. This is
necessary because today this information is guaranteed by the presence
of list of route segments in the scrutiny output, and in a future change
those route segments will be removed. This error type thus must carry
all the necessary information for diagnosing and resolving the issue it
signifies.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1094672
Original-Revision: 9bfca821527adac0753b2cfaefd1884599976eb9
GitOrigin-RevId: 2e3f7aa28bc69e27d1abd92f1c1a9373230171de
Change-Id: I3b6878fcaeb658b39cb58813d8f79a871d12ce3f
1 file changed
tree: 375503e4738ac3ebd9effe4662f0e4f2ee6d7dd1
  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 via the IRC channel #fuchsia on Freenode.

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.