[roll] Roll fuchsia [fxfs] add a log for vmo op range failure in replay If we get an error back from op_range, print a warning with the error. I have a theory that if this fails then the profile tests will get stuck waiting for committed_bytes to change from zero for whatever file it fails on. This should help confirm that theory the next time this flakes if that is right. Original-Bug: 484869733 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1550564 Original-Revision: 4ce2be5715fd589cb9102a6a5e0bee9d1d0a0cdb GitOrigin-RevId: fe2152fa6fb4446a7b48cedc169c3422d1283319 Change-Id: Ia1f150e352891d9a7db35aa5de12faa4a15ba291
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 in one of the communication channels documented at get involved.
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.