Skip to content

Conversation

@christopherfujino
Copy link
Contributor

Moved one test from integration.shard/bash_entrypoint_test.dart and the complete file of integration.shard/macos_content_validation_test.dart to a new shard, mac_arm.shard/. Also created a new builder in .ci.yaml, copying Mac tool_integration_tests 1_4, while deleting the goldctl dependency.

@flutter-dashboard flutter-dashboard bot added c: contributor-productivity Team-specific productivity, code health, technical debt. tool Affects the "flutter" command-line tool. See also t: labels. labels Apr 12, 2022
Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

I don't think mac_arm.shard makes sense, these tests need to run on x64 as well...
Should also include ios_content_validation_test for the simulator arch tests.

@christopherfujino
Copy link
Contributor Author

christopherfujino commented Apr 12, 2022

I don't think mac_arm.shard makes sense, these tests need to run on x64 as well... Should also include ios_content_validation_test for the simulator arch tests.

host_cross_arch.shard?

@christopherfujino christopherfujino force-pushed the shard-out-mac-arm-tests branch from 4130db4 to 1f6a80c Compare April 12, 2022 20:03
Copy link
Contributor

@keyonghan keyonghan left a comment

Choose a reason for hiding this comment

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

Config LGTM, but we need to add the test ownership to pass the test.

@christopherfujino
Copy link
Contributor Author

Config LGTM, but we need to add the test ownership to pass the test.

Should this be added as a comment near the end of TESTOWNERS? I'm not sure what's going on in that file.

@keyonghan
Copy link
Contributor

Config LGTM, but we need to add the test ownership to pass the test.

Should this be added as a comment near the end of TESTOWNERS? I'm not sure what's going on in that file.

That's right.

@christopherfujino
Copy link
Contributor Author

cc @Jasguerrero for context, regarding our 1:1 conversation, this is what it currently takes to create a new test shard.

.ci.yaml Outdated
Comment on lines 2924 to 2926
{"dependency": "android_sdk", "version": "version:31v8"},
{"dependency": "chrome_and_driver", "version": "version:98.1"},
{"dependency": "open_jdk", "version": "11"},
Copy link
Member

Choose a reason for hiding this comment

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

I know all the tasks have android_sdk and chrome_and_driver and open_jdk but I don't think they are needed for these tests. Can you try removing them and see if it passes? I've been meaning to audit all of them.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

SGTM, i already removed goldctl

Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

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

LGTM, thanks Chris

@christopherfujino
Copy link
Contributor Author

New builder was created but no builds scheduled yet. For monitoring: https://ci.chromium.org/p/flutter/builders/staging/Mac%20tool_host_cross_arch_tests

@christopherfujino
Copy link
Contributor Author

First seven builds all green, looks like a success https://ci.chromium.org/p/flutter/builders/staging/Mac%20tool_host_cross_arch_tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants