Relands https://github.com/flutter/flutter/pull/146181.
Just 3 commits:
1. a revert of the revert
2. the fix described in https://github.com/flutter/flutter/pull/146181#issuecomment-2038238869
3. updating two postsubmit tests from Java 11 to 17, as that is required for this new AGP version.
I've verified that `flutter build apk --flavor paid --debug` fails in `dev/integration_tests/flavors/` with the error in ci without (2), and succeeds with it.
I've also verified that the `dev/benchmarks/complex_layout` app builds successfully with Java 17.
That covers all the postsubmits that failed according [to the dashboard](https://flutter-dashboard.appspot.com/#/build).
* Adds support for `flutter test --wasm`.
* The test compilation flow is a bit different now, so that it supports compilers other than DDC. Specifically, when we run a set of unit tests, we generate a "switchboard" main function that imports each unit test and runs the main function for a specific one based off of a value set by the JS bootstrapping code. This way, there is one compile step and the same compile output is invoked for each unit test file.
* Also, removes all references to `dart:html` from flutter/flutter.
* Adds CI steps for running the framework unit tests with dart2wasm+skwasm
* These steps are marked as `bringup: true`, so we don't know what kind of failures they will result in. Any failures they have will not block the tree at all yet while we're still in `bringup: true`. Once this PR is merged, I plan on looking at any failures and either fixing them or disabling them so we can get these CI steps running on presubmit.
This fixes https://github.com/flutter/flutter/issues/126692
Switch hot_mode_dev_cycle_linux__benchmark to run in postsubmit.
*List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*
Part of https://github.com/flutter/flutter/issues/145242
*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
This is required to match a rename being made for the devices in firebase lab.
Also removed `version=24` entry, since thats not supported on Nexus5x, per the firebase team.
Bug:b/322830672
*Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*
*List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*
*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
Reverts: flutter/flutter#145224
Initiated by: hellohuanlin
Reason for reverting: breaks the tree
Original PR Author: hellohuanlin
Reviewed By: {gmackall, jmagman}
This change reverts the following previous change:
Reland https://github.com/flutter/flutter/pull/144745, which got reverted due to Android lockfile. Fixed by `dart dev/tools/bin/generate_gradle_lockfiles.dart`
*List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*
Fixes https://github.com/flutter/flutter/issues/143534
Fixes https://github.com/flutter/flutter/issues/143257
*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
These tests were failing in postsubmit after a change to `packages/flutter_tools`. We should run these in presubmit when `packages/flutter_tools` changes.
Windows Defender sometimes kills the `Windows_arm64 plugin_test_windows` test process, causing the test to hang until it times out after 30 minutes. This reduces the test timeout to 900 seconds (15 minutes) to recover from this scenario faster.
Test timeout duration was chosen by looking at successful duration percentiles in the last 100 days:
duration_seconds_p90 | duration_seconds_p99 | duration_seconds_max
-- | -- | --
532 | 545 | 576
BigQuery SQL:
```sql
WITH
successful_steps AS (
SELECT
b.id,
TIMESTAMP_DIFF(s.end_time, s.start_time, SECOND) AS duration_seconds,
FROM cr-buildbucket.flutter.builds AS b, UNNEST(steps) AS s
WHERE
create_time > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 100 DAY)
AND regexp_substr(input.gitiles_commit.project, '[^\\/]+$') = 'flutter'
AND builder.project || '/' || builder.bucket || '/' || builder.builder
= 'flutter/prod/Windows_arm64 plugin_test_windows'
AND name = 'run plugin_test_windows'
AND s.status = 'SUCCESS'
)
SELECT
percentiles[offset(90)] AS duration_seconds_p90,
percentiles[offset(99)] AS duration_seconds_p99,
duration_seconds_max
FROM (
SELECT
APPROX_QUANTILES(duration_seconds, 100) AS percentiles,
MAX(duration_minutes) AS duration_seconds_max
FROM successful_steps
);
```
`test_timeout_secs` is documented here: https://github.com/flutter/cocoon/blob/main/CI_YAML.md
Part of https://github.com/flutter/flutter/issues/145072
Part of https://github.com/flutter/flutter/issues/143616
Without this these tests only run on postsubmit which means we can't get gold results on PRs.
This was reverted because it landed after an engine change that broke flutter tester. That change has since been reverted.
Almost all of our devicelab devices are on iOS 17 now, so let's use them exclusively so we can verify that tests pass consistently on iOS 17.
Fixes https://github.com/flutter/flutter/issues/144020.
The Windows arm64 builds were all moved to bringup because new test beds not properly provisioned were added to the production pool.
Those new test beds are now fully validated but still running on staging pool to ensure they are not introducing noise in the prod pools.
Bug: https://github.com/flutter/flutter/issues/143180
The certs dependency was added in 2020 as a workaround for missing certificates in win 10 images. These dependency is not required for windows arm64 builds because they are running on win 11.
My understanding is I can do this safely because the task is marked `bringup: true`?
Next PR will remove `bringup` and take down the old tasks.
Partial work towards https://github.com/flutter/flutter/issues/142178.
It shouldn't be very common for x64 example projects to not build if they built on arm64. We have other tool tests that would probably catch those issues in presubmit.
Instead run them on postsubmit only to free up limited x64 staging resources.
Follow up from #141206
*Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*
*List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*
*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
Changes to use the proto.textpb config file as the version of the emulator device and show the cipd dependency version in the dependencies so devs know it can be updated.
*List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*
Fixes https://github.com/flutter/flutter/issues/142261
*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
