Skip to content

[ci] Add x64 specific Windows platform #5133

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

Merged
merged 1 commit into from
Oct 13, 2023
Merged

[ci] Add x64 specific Windows platform #5133

merged 1 commit into from
Oct 13, 2023

Conversation

loic-sharma
Copy link
Member

@loic-sharma loic-sharma commented Oct 12, 2023

This begins to migrate the Windows CI tests to use a new x64 specific Windows platform. For now these duplicate the existing tests in bringup mode.

A subsequent pull request (#5141) will complete the migration by removing the old Windows tests and removing the bringup from the new x64 specific tests. Here are the resulting changes from both steps of the migration: main...loic-sharma:flutter-packages:windows_x64_ci_finalize

In the future, a new platform will be added for Windows Arm64 tests.

Prepares for flutter/flutter#129813

Subsequent pull requests:

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

]
device_type: none
os: Windows
cpu: x86
Copy link
Member Author

Choose a reason for hiding this comment

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

This line was added from the existing windows platform properties.

@loic-sharma loic-sharma marked this pull request as ready for review October 12, 2023 18:18
@loic-sharma loic-sharma changed the title [ci] Rename the CI's Windows x64 platform [ci] Add x64 specific Windows platform Oct 12, 2023
Copy link
Contributor

@stuartmorgan-g stuartmorgan-g left a comment

Choose a reason for hiding this comment

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

LGTM

I forgot we're still using VS 2019. We should probably look into getting that updated; I don't know if infra has 2022 available for us to depend on.

@loic-sharma
Copy link
Member Author

@stuartmorgan Supporting VS2022 is tracked by flutter/flutter#96138. FWIW, VS2019 will receive security updates until April 2029.

@loic-sharma loic-sharma added the autosubmit Merge PR when tree becomes green via auto submit App label Oct 13, 2023
@auto-submit auto-submit bot merged commit 68eedfd into main Oct 13, 2023
@auto-submit auto-submit bot deleted the windows_x64_ci branch October 13, 2023 20:55
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Oct 16, 2023
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request Oct 16, 2023
flutter/packages@fd84e65...872d6d2

2023-10-16 49699333+dependabot[bot]@users.noreply.github.com Bump github/codeql-action from 2.22.2 to 2.22.3 (flutter/packages#5151)
2023-10-15 engine-flutter-autoroll@skia.org Roll Flutter from 3865e49 to b00216b (34 revisions) (flutter/packages#5147)
2023-10-13 737941+loic-sharma@users.noreply.github.com [ci] Add x64 specific Windows platform  (flutter/packages#5133)
2023-10-13 49699333+dependabot[bot]@users.noreply.github.com Bump github/codeql-action from 2.22.1 to 2.22.2 (flutter/packages#5138)
2023-10-13 engine-flutter-autoroll@skia.org Roll Flutter from 83134ac to 3865e49 (80 revisions) (flutter/packages#5140)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem@google.com,rmistry@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
auto-submit bot pushed a commit that referenced this pull request Oct 20, 2023
#5133 began to migrate the Windows CI tests to use a new x64 specific Windows platform. This completes the migration by removing the old Windows tests and removing `bringup` from the new x64 specific tests.

To see the resulting changes from both steps of the migration, refer to: 0bddb16...loic-sharma:flutter-packages:windows_x64_ci_finalize_2#diff-9e73abde9fff445f31e5928e80d2d3f88847e02fd8f76d46f66f147fdc82786d

Prepares for flutter/flutter#129813

Previous stacked pull request: #5133
Next stacked pull request: #5142
auto-submit bot pushed a commit that referenced this pull request Oct 20, 2023
Add build-only Windows Arm64 CI tests, mirroring the way we handle multi-arch for macOS.

Completes: flutter/flutter#129813

Previous stacked pull requests:
* #5133
* #5174
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autosubmit Merge PR when tree becomes green via auto submit App
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants