8000 Build/Archive/Test refactoring of CI testing needs implemention of the test phase · Issue #116906 · flutter/flutter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Build/Archive/Test refactoring of CI testing needs implemention of the test phase #116906

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.

Sign up for GitHub

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

Jump to bottom
Closed
whesse opened th 8000 is issue Dec 12, 2022 · 3 comments
Closed

Build/Archive/Test refactoring of CI testing needs implemention of the test phase #116906

whesse opened this issue Dec 12, 2022 · 3 comments
Assignees
@eyebrowsoffire
Labels
a: tests "flutter test", flutter_test, or one of our tests ⏳ Bot is counting down the days until it unassigns the issue team-infra Owned by Infrastructure team

Comments

@whesse
Copy link
Contributor
whesse commented Dec 12, 2022

The issue
#81855

tracks the refactoring of Flutter CI testing to separate the building of Flutter engine artifacts and
the running of tests on those artifacts.

The implementation of the testers that will run the tests can be tracked here.
These are running on the LUCI test system, where all running jobs are called "builders", so
they can also be called builders or test builders.

Work is currently proceeding on a initial implementation that supports also a
logical monorepo checkout of Dart SKD, Flutter engine, and Flutter framework.

https://flutter-review.git.corp.google.com/c/recipes/+/36400
https://flutter-review.git.corp.google.com/c/recipes/+/37200

This issue also tracks the design of the testing, including:

Can the existing flutter/flutter_drone recipe, currently used for testing, be extended to handle
the testing done after this refactoring, instead of creating a new recipe?
@whesse whesse added a: tests "flutter test", flutter_test, or one of our tests team-infra Owned by Infrastructure team labels Dec 12, 2022
@whesse whesse mentioned this issue Dec 12, 2022
Closed
@eyebrowsoffire eyebrowsoffire self-assigned this Jan 31, 2023
@flutter-triage-bot flutter-triage-bot bot added the ⏳ Bot is counting down the days until it unassigns the issue label Jul 30, 2023
@flutter-triage-bot
Copy link

This issue is assigned to @eyebrowsoffire but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

@whesse
Copy link
Contributor Author
whesse commented Jul 31, 2023

Running tests in engine_v2 builders is implemented, and further development of it will be tracked with individual issues about each specific new type of testing being supported on engine_v2 builders.

The current support for running tests in engine_v2 builders is in two recipes:
https://flutter.googlesource.com/recipes/+/refs/heads/main/recipes/engine_v2/tester.py
and
https://flutter.googlesource.com/recipes/+/refs/heads/main/recipes/engine_v2/tester_engine.py

@whesse whesse closed this as completed Jul 31, 2023
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@eyebrowsoffire eyebrowsoffire

Labels
a: tests "flutter test", flutter_test, or one of our tests ⏳ Bot is counting down the days until it unassigns the issue team-infra Owned by Infrastructure team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whesse @eyebrowsoffire
0