-
Notifications
You must be signed in to change notification settings - Fork 12.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
CI: Migrate to windows-2022 #92948
Comments
Issue: dos2unix does not work The
I haven't investigated much, but I suspect it might be a conflict with one of our manually downloaded msys/mingw things. actions/runner-images#594 also contains some context. As a side note: The install-mingw step installs and updates a bunch of packages, which the 2019 images do not (all the packages are already installed and up-to-date). |
This comment has been minimized.
This comment has been minimized.
Issue: errors in run-make-fulldeps Many of the run-make-fulldeps tests are failing. Many are probably related to the same underlying problem of handling gnu vs windows paths. x86_64-pc-windows-gnu and x86_64-pc-windows-msvc fail with about 125 errors, roughly of this form:
|
It probably needs an update but I'll look at it when I get home. Any recommendations? |
Unfortunately I don't know why it is failing. We install a custom mingw and msys2 (https://github.com/rust-lang/rust/blob/master/src/ci/scripts/install-mingw.sh and https://github.com/rust-lang/rust/blob/master/src/ci/scripts/install-msys2.sh), which might be interfering with the system-provided binaries. Or it could be something else, I haven't investigated. |
I'd like to have a go at getting this working @rustbot claim |
@ehuss is there something that I need to do to get access to Server 2022 build agents? |
First blocking issue: CI currently installs Clang14 to build LLVM: rust/src/ci/scripts/install-clang.sh Line 13 in ce3263e
But the STL in VS 2022 requires Clang 16+: I've raised this on Zulip with wg-llvm: https://rust-lang.zulipchat.com/#narrow/stream/187780-t-compiler.2Fwg-llvm/topic/Updating.20the.20version.20of.20LLVM.20used.20to.20build.20LLVM.3F/near/434435620 |
Pinged t-infra for XL Server 2022 images: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Availability.20of.20XL.20Windows.20Server.202022.20runners/near/435038176 |
Current statusDraft PR: #124174 Pending FixesI'm waiting on the intra team to help out with two things (would appreciate some help to expidite these): There also one test that was failing which I've submitted a PR to fix: #124378 Build statusWorking
Works with updated Clang (16+)
Broken
|
This was only partially fixed. |
Use Server 2022 in CI for mingw jobs From my [previous testing](rust-lang/rust#92948 (comment)), there is nothing blocking using Server 2022 for the Windows MinGW jobs. This change: * Adds new `os` entries for Server 2022. * Renamed the Server 2019 `os` entries (as we'll be removing these over time). * Moves the mingw jobs to Server 2022 and leaves the msvc jobs on Server 2019. Partially fixes #92948
Upgrade pre-built Clang used in MSVC and MacOS builds, move MSVC builds to Server 2022 Fixes rust-lang#92948 Example working MacOS and Windows builds: <https://github.com/rust-lang/rust/actions/runs/8989360201> Using Server 2022 for AArch64 MSVC is blocked by <llvm/llvm-project#81849>. I'll see if I can work around the issue in a follow up PR.
Upgrade pre-built Clang used in MSVC and MacOS builds, move MSVC builds to Server 2022 Fixes rust-lang#92948 Example working MacOS and Windows builds: <https://github.com/rust-lang/rust/actions/runs/8989360201> Using Server 2022 for AArch64 MSVC is blocked by <llvm/llvm-project#81849>. I'll see if I can work around the issue in a follow up PR.
Upgrade pre-built Clang used in MSVC and MacOS builds, move MSVC builds to Server 2022 Fixes rust-lang#92948 Example working MacOS and Windows builds: <https://github.com/rust-lang/rust/actions/runs/8989360201> Using Server 2022 for AArch64 MSVC is blocked by <llvm/llvm-project#81849>. I'll see if I can work around the issue in a follow up PR.
Upgrade pre-built Clang used in MSVC and MacOS builds, move MSVC builds to Server 2022 Fixes rust-lang#92948 Example working MacOS and Windows builds: <https://github.com/rust-lang/rust/actions/runs/8989360201> Using Server 2022 for AArch64 MSVC is blocked by <llvm/llvm-project#81849>. I'll see if I can work around the issue in a follow up PR.
Upgrade pre-built Clang used in MSVC and MacOS builds, move MSVC builds to Server 2022 Fixes rust-lang#92948 Example working MacOS and Windows builds: <https://github.com/rust-lang/rust/actions/runs/8989360201> Using Server 2022 for AArch64 MSVC is blocked by <llvm/llvm-project#81849>. I'll see if I can work around the issue in a follow up PR.
Use Server 2022 in CI for mingw jobs From my [previous testing](rust-lang/rust#92948 (comment)), there is nothing blocking using Server 2022 for the Windows MinGW jobs. This change: * Adds new `os` entries for Server 2022. * Renamed the Server 2019 `os` entries (as we'll be removing these over time). * Moves the mingw jobs to Server 2022 and leaves the msvc jobs on Server 2019. Partially fixes #92948
Use Server 2022 in CI for mingw jobs From my [previous testing](rust-lang/rust#92948 (comment)), there is nothing blocking using Server 2022 for the Windows MinGW jobs. This change: * Adds new `os` entries for Server 2022. * Renamed the Server 2019 `os` entries (as we'll be removing these over time). * Moves the mingw jobs to Server 2022 and leaves the msvc jobs on Server 2019. Partially fixes #92948
GitHub is starting a migration of
windows-latest
towindows-2022
:https://github.blog/changelog/2022-01-11-github-actions-jobs-running-on-windows-latest-are-now-running-on-windows-server-2022/
actions/runner-images#4856
Migration starts now, and should finish by March 6. It is not clear if that timetable includes the
-xl
runners. Based on the fact that theubuntu-latest-xl
runners have not yet migrated to 20.04, which was "completed" in 2021-03-18 (and it is now 2022-01-15), the timing for the-xl
images might be much slower.UPDATE from GitHub: Our first goal is to GA Windows 2022 this quarter and then we will start the process of getting the XL pools ready.
It may be possible to lock to an older version with
windows-2019-xl
(as it appears those version-specific qualifiers work with ubuntu), but I have not tested that.I have started testing some builds in 2022 and they are not going well, I'll try to document some issues here.
The text was updated successfully, but these errors were encountered: