-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[Fuchsia] Use chromium test-scripts to download images and execute tests #49650
Conversation
12db7f8
to
e3b9d9e
Compare
4edc85f
to
e441a2a
Compare
# This file is expected to be executed from src/flutter/. | ||
|
||
|
||
# TODO(https://github.com/flutter/flutter/issues/140179): Execute all the tests |
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.
Once this TODO is done, we can delete the Linux Fuchsia FEMU builds
\cc @keyonghan as FYI
@keyonghan this requires a second Flutter hacker to review. Can you take a look? |
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.
Some lint errors need a fix: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8759159184604771825/+/u/test:_pylint/stdout
Yeap, I am fixing the pylint. |
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
Thank you all. |
FYI we ended up needing to update the engine_v2 dimensions as well. I sent #49770 as it's flaking on CI where it runs on bots without KVM. |
…141464) flutter/engine@ef2cf86...0ac8215 2024-01-12 68449066+zijiehe-google-com@users.noreply.github.com [Fuchsia] Use chromium test-scripts to download images and execute tests (flutter/engine#49650) 2024-01-12 skia-flutter-autoroll@skia.org Roll Skia from e04ca400c5d8 to 2bc5d2ee9896 (1 revision) (flutter/engine#49761) 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 bdero@google.com,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
@@ -1101,5 +1117,16 @@ hooks = [ | |||
'third_party/impeller-cmake-example', | |||
'--setup', | |||
] | |||
}, | |||
{ |
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.
How big are these system images? Most Flutter engine developers aren't developing/testing for Fuchsia, so if these are bigger than a few MB, this download should be gated behind a gclient custom var or env variable that is set on CI.
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.
It's fairly large. We discussed if it was a common practice to have a download_fuchsia_deps
to consider both host_os
and target_os
, but haven't found a similar approach for other platforms. #49650 (comment)
@@ -0,0 +1,53 @@ | |||
#!/usr/bin/env python3 | |||
# Copyright (c) 2024, the Flutter project authors. All rights reserved. |
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.
The copyright year should be 2013 for all copyright headers in the engine repo.
@@ -0,0 +1,59 @@ | |||
#!/usr/bin/env python3 | |||
# Copyright (c) 2024, the Flutter project authors. All rights reserved. |
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.
The copyright year should be 2013 for all copyright headers in the engine repo.
@zijiehe-google-com I'm going to revert this as there's a few other follow up comments that should be addressed as well. If there's any issues with the follow ups, it'll make it easier to revert if this one PR instead of several PRs. |
…xecute tests" (#49772) Reverts #49650 Initiated by: CaseyHillers This change reverts the following previous change: Original Description: This change requires flutter/buildroot#811, and can be executed from buildroot by ``` python3 flutter/tools/fuchsia/with_envs.py flutter/testing/fuchsia/run_tests.py ``` Bug: flutter/flutter#140179 - [V] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [V] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [V] I read and followed the [Flutter Style Guide] and the [C++, Objective-C, Java style guides]. - [V] I listed at least one issue that this PR fixes in the description above. - [V] I added new tests to check the change I am making or feature I am adding, or the PR is [test-exempt]. See [testing the engine] for instructions on writing and running engine tests. - [V] I updated/added relevant documentation (doc comments with `///`). - [V] I signed the [CLA]. - [V] All existing and new tests are passing. [C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
SG, I will merge #49650 into the change as well. |
…cute tests (#49847) This change is a redo of #49650. https://github.com/zijiehe-google-com/engine/compare/de5c713..main should show the diff between this and the original change. Following paragraph is copied from the original change. This change requires flutter/buildroot#811, and can be executed from buildroot by ``` python3 flutter/tools/fuchsia/with_envs.py flutter/testing/fuchsia/run_tests.py ``` Bug: flutter/flutter#140179 ## Pre-launch Checklist - [V] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [V] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [V] I read and followed the [Flutter Style Guide] and the [C++, Objective-C, Java style guides]. - [V] I listed at least one issue that this PR fixes in the description above. - [V] I added new tests to check the change I am making or feature I am adding, or the PR is [test-exempt]. See [testing the engine] for instructions on writing and running engine tests. - [V] I updated/added relevant documentation (doc comments with `///`). - [V] I signed the [CLA]. - [V] All existing and new tests are passing.
…s and execute tests" (#49908) Reverts #49847 Initiated by: zanderso This change reverts the following previous change: Original Description: This change is a redo of #49650. https://github.com/zijiehe-google-com/engine/compare/de5c713..main should show the diff between this and the original change. Following paragraph is copied from the original change. This change requires flutter/buildroot#811, and can be executed from buildroot by ``` python3 flutter/tools/fuchsia/with_envs.py flutter/testing/fuchsia/run_tests.py ``` Bug: flutter/flutter#140179 - [V] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [V] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [V] I read and followed the [Flutter Style Guide] and the [C++, Objective-C, Java style guides]. - [V] I listed at least one issue that this PR fixes in the description above. - [V] I added new tests to check the change I am making or feature I am adding, or the PR is [test-exempt]. See [testing the engine] for instructions on writing and running engine tests. - [V] I updated/added relevant documentation (doc comments with `///`). - [V] I signed the [CLA]. - [V] All existing and new tests are passing.
This change requires flutter/buildroot#811, and can be executed from buildroot by
Bug: flutter/flutter#140179
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.