[roll] Roll fuchsia [location] Fix flaky emergency test

Sometimes the `reports_elapsed_time_to_cobalt_on_success` test winds up
getting scheduled in such a way that the latency elapsed rounds up to 2
milliseconds of wall-clock time instead of exactly zero milliseconds,
which causes the assertion to fail.

Since we're not injecting a time source, just assert that this is some
integer value and don't try to assert that the particular value is zero.

Original-Fixed: 109676
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/730462
Original-Revision: 6085b91ef062e57183cf5ae99ca3daa994793d1e
GitOrigin-RevId: 7ff04270c691b7604e2f132a0ba4d6562e303444
Change-Id: I5dcfb581c44ae872ec665055421bbd9137825b50
1 file changed
tree: 5ef084b64923715c97208a8c1c6874306774648c
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.