[roll] Roll fuchsia [fx] Suggest fx gen when fx.config fails to source but args.gn exists

When sourcing `fx.config` fails in `fx-build-config-load`, we previously
always suggested running `fx set`. However, if the user already has a
build setup (indicated by the presence of `args.gn`), running `fx set`
might clobber their existing configuration.

This change updates the error message to suggest `fx gen` if `args.gn`
exists, and `fx set` only if it doesn't.

This addresses a follow-up comment on fxr/1593069.

Added a new test `fx_config_load_test` to verify both cases.

Original-Bug: 497047464
Test: tools/devshell/tests/lib/script_runner.sh ../subcommands/fx_config_load_test
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1594368
Original-Revision: 517a576674aa77f9387e674f3c58f9e73041523d
GitOrigin-RevId: bca8de765227a3da41b40573bf53e910d6d2d2f1
Change-Id: If65d7a9b73e6db864b89e6b9ca25ab9e5c1ff957
1 file changed
tree: c1fcbd5c4e1549ef84e58b0ec729b3167134d8d0
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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 in one of the communication channels documented at get involved.

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.