[roll] Roll fuchsia [hermetic-env] Pass in $HOME to hermetic env.

hermetic-env seems mostly concerned with ensuring the Python execution
does not use packages installed on the local system rather than
providing a true hermetic execution environment.

As more developer tooling is written in Python, it makes sense to allow
access to the user's HOME directory when using hermetic-env in
fuchsia-vendored-python.

This fixes the issue where the new Python fx test lacks symbolization;
the symbolizer looks for a symbol index under $HOME, which must be
present for it to work.

Original-Fixed: b/299543238
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/921732
Original-Revision: 191ff2633c6948f324c7eebebf9f469357150925
GitOrigin-RevId: 58df8769bea4a7462db3e13e6f9ccd871f31e692
Change-Id: I7e42473d768c72b19a5c2f5d0b5e50e6307f4792
1 file changed
tree: c7af7992b064849fd2a56c0579be3662f5c04538
  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.