[roll] Roll fuchsia [python] Ensure validation dependencies are not included in library_infos.json This prepares for rolling a new GN version that does not walk validation dependencies when performing metadata walks (see associated bug for details). This ensures that library_infos.json from the mypy validation action itself do not end up propagating data to their dependents. After this CL is submitted, comparing out/default after using `gn gen` with the old and new GN binary show no more differences in .library_infos.json files. In all cases, the differences were that the entries in generated_file() outputs were in different order, because including validation deps in the walk changes the total order of the result. The final sorted result is unchanged though (but these files are generated by GN directly and cannot be sorted by it). Original-Original-Bug: 517150685 Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1630237 Original-Original-Revision: 5458c63deec050b09585a6149eacceee38dd27ae GitOrigin-RevId: eb8551cf81f90fa1adc1e13392bc4f1c179bad3f Change-Id: Ifd1000a24e118594ad6b216323802ec036603682
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.