[roll] Roll fuchsia [sanitizers] Temporarily disable ASan container checking for outgoing

The bringup.riscv64-asan builder seems to be consistently failing with
a container-check in OutgoingDirectory::MakePath. After debugging for a
couple of days, I haven't been able to find anything that indicates this
is an actual bug, so this may likely be a false positive from something
else linked in that isn't built with ASan. This occurs after
https://github.com/llvm/llvm-project/pull/75845 landed which enables
container-checking for all std::string allocators.

For now, let's temporarily disable container checking for this
source_set to unblock migrating the bringup.riscv64-asan builder.

Original-Bug: b/322528969
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/982654
Original-Revision: 20e66a58e421908864acfe5a11b229172378b98c
GitOrigin-RevId: 6ca19ec7ea6d0033fdf4d8bac9b87b1858e17b2f
Change-Id: I62e4d4b79807db717d6b5f72b4b43bf70911fa11
1 file changed
tree: ee2a0815a91f3f54e61b32550f96ee12dfe7adca
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.