-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Treat missing --local-engine-host as fatal on CI-like systems. #132707
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
Treat missing --local-engine-host as fatal on CI-like systems. #132707
Conversation
christopherfujino
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
auto label is removed for flutter/flutter/132707, due to - The status or check suite Mac tool_tests_commands has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
/cc @whesse ^ |
|
No errors have shown up in the Dart CI after this change landed. |
|
A fix for the flutter engine CI errors is at https://flutter-review.googlesource.com/c/recipes/+/49620 Please log in to this review host, which creates an account, so you can be added as CC on reviews on this site. A further use of --local-engine with a matching --local-engine-host is in the devicelab drone runners, which get their local engine value from an environment variable LOCAL_ENGINE, with no matching environment variable LOCAL_ENGINE_HOST. They pass the --local-engine flag to the devicelab test runner, which has had the corresponding flag local-engine-host added in https://github.com/flutter/flutter/blob/master/dev/devicelab/lib/command/test.dart#L40. I don't know why these have not started failing since this CL landed. It may be that no CI builders pass the LOCAL_ENGINE flag to these drones any more, since engine testing has migrated to engine_v2 which does not use local-engine. If this is the case, then the support for LOCAL_ENGINE should be removed from the recipe, instead of adding support for LOCAL_ENGINE_HOST and providing it. |
Partial work towards #132245.
The goal here is to "sniff" out any missing pieces that would block engine builds, rolls, benchmarks and so on before requiring humans to provide the parameter. The implementation is based on a short discussion with @christopherfujino:
@matanlurey:
@christopherfujino: