Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move verbose to environment.verbose, pass to ninja --verbose if provided. #52619

Merged

Conversation

matanlurey
Copy link
Contributor

@matanlurey matanlurey commented May 7, 2024

Closes flutter/flutter#147894.

While doing this PR I realized we were basically passing (bool verbose, Envrionment) as a tuple around, so I just moved the concept into Environment directly, and made the necessary code changes across the tool and tests.

To clarify, this does not mimic the output of ninja --verbose today, because we also don't stream the output directly, and instead do terminal magic. Combined with a hypothetical fix for flutter/flutter#147903, this would work exactly the same as before.

/cc @loic-sharma @johnmccutchan

Copy link
Member

@loic-sharma loic-sharma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -66,13 +66,13 @@ void main(List<String> args) async {
platform: const LocalPlatform(),
processRunner: ProcessRunner(),
logger: Logger(),
verbose: verbose,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optional: as a further cleanup, the verbosity could just be encoded in the log level of the Logger() on the line above. It's currently set in https://github.com/flutter/engine/blob/main/tools/engine_tool/lib/src/commands/command_runner.dart#L106, but could just as well be set here.

Copy link
Contributor Author

@matanlurey matanlurey May 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense, but probably what I would do is something like Logger(verbose: true) and have Logger set itself up versus trying to overload Logger's log severity (where verbose isn't really a thing) with the app-wide verbosity flag.

Let me send a follow-up PR and we can chomp on that a bit.

@matanlurey matanlurey added the autosubmit Merge PR when tree becomes green via auto submit App label May 7, 2024
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label May 7, 2024
Copy link
Contributor

auto-submit bot commented May 7, 2024

auto label is removed for flutter/engine/52619, due to - The status or check suite Linux linux_unopt has failed. Please fix the issues identified (or deflake) before re-applying this label.

@matanlurey matanlurey added the autosubmit Merge PR when tree becomes green via auto submit App label May 7, 2024
@auto-submit auto-submit bot merged commit 66ee93c into flutter:main May 7, 2024
29 checks passed
@matanlurey matanlurey deleted the refactor-verbose-and-pass-to-ninja branch May 7, 2024 19:44
auto-submit bot pushed a commit that referenced this pull request May 7, 2024
…r. (#52624)

Based on @zanderso's feedback here: #52619 (comment).

I think this is the most succinct way to setup logging, it also doesn't seem to make sense to allow the level to be configured at runtime, so boom.
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request May 7, 2024
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request May 7, 2024
…147943)

flutter/engine@42898e0...1fe835b

2024-05-07 98614782+auto-submit[bot]@users.noreply.github.com Reverts "Add host_profile_arm64 and host_release_arm64 local engine configurations. (#52620)" (flutter/engine#52630)
2024-05-07 matanlurey@users.noreply.github.com Move `verbose` to `environment.verbose`, pass to `ninja --verbose` if provided. (flutter/engine#52619)
2024-05-07 chinmaygarde@google.com Add host_profile_arm64 and host_release_arm64 local engine configurations. (flutter/engine#52620)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry@google.com,zra@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autosubmit Merge PR when tree becomes green via auto submit App
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[et] Forward --verbose to ninja
3 participants