{aarch64,x86_64}-pc-windows-gnullvm: build host tools#140772
{aarch64,x86_64}-pc-windows-gnullvm: build host tools#140772bors merged 1 commit intorust-lang:masterfrom
Conversation
|
r? @marcoieni rustbot has assigned @marcoieni. Use |
|
This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. |
|
Forgot to include |
ok, so I guess we need to try this, right? @bors try |
{aarch64,x86_64}-*-windows-gnullvm: build host tools
This will require MCP, but I suppose we need to know how long it takes to build first.
I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.
`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.
Almost every commit is self-contained, so let me know if I should split them into separate PRs.
try-job: dist-windows-gnullvm
This comment has been minimized.
This comment has been minimized.
|
maybe you need to add the job to the |
|
💥 Test timed out |
|
Oh, right. Totally forgot about it. |
|
@bors try |
{aarch64,x86_64}-*-windows-gnullvm: build host tools
This will require MCP, but I suppose we need to know how long it takes to build first.
I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.
`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.
Almost every commit is self-contained, so let me know if I should split them into separate PRs.
try-job: dist-windows-gnullvm
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
Unfortunately, free CI runners are not as capable as I had hoped. I've split the jobs now, but dunno if this will be acceptable. |
yes, we prefer multiple free runner compared to 1 large runner 👍 @bors try |
{aarch64,x86_64}-*-windows-gnullvm: build host tools
This will require MCP, but I suppose we need to know how long it takes to build first.
I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.
`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.
Almost every commit is self-contained, so let me know if I should split them into separate PRs.
try-job: dist-aarch64-windows-gnullvm
try-job: dist-x86_64-windows-gnullvm
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
@bors try |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 044514e (parent) -> d1d8e38 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard d1d8e386c5e84c4ba857f56c3291f73c27e2d62a --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (d1d8e38): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary -2.5%, secondary 0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 693.624s -> 692.944s (-0.10%) |
…Simulacrum Add windows-gnullvm hosts to the manifest I made a mistake testing rust-lang#140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
…Simulacrum Add windows-gnullvm hosts to the manifest I made a mistake testing rust-lang#140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
…Simulacrum Add windows-gnullvm hosts to the manifest I made a mistake testing rust-lang#140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
…Simulacrum Add windows-gnullvm hosts to the manifest I made a mistake testing rust-lang#140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
…Simulacrum Add windows-gnullvm hosts to the manifest I made a mistake testing rust-lang#140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
Rollup merge of #143031 - mati865:push-mutywntmvomx, r=Mark-Simulacrum Add windows-gnullvm hosts to the manifest I made a mistake testing #140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
Add windows-gnullvm hosts to the manifest I made a mistake testing rust-lang/rust#140772 only with `rustup-toolchain-install-master` which doesn't care about the manifests. This means windows-gnullvm self-hosting will have to wait one more release, unless this change is backported to beta and a new beta release is made, which doesn't seem worth the trouble.
Revert rust-lang#143031 and rust-lang#140772 due to the issue with host tools reported in https://github.com/rust-lang/rust/issue/144533. This reverts commits 508021a and d577b39.
Revert rust-lang#143031 and rust-lang#140772 due to the issue with host tools reported in https://github.com/rust-lang/rust/issue/144533. This reverts commits 508021a and d577b39. CC rust-lang#145435
Revert rust-lang#143031 and rust-lang#140772 due to the issue with host tools reported in https://github.com/rust-lang/rust/issue/144533. This reverts commits 508021a and d577b39. The decision was made in rust-lang#144659 (comment). Tracking issue: rust-lang#145435
Revert <rust-lang#143031> and <rust-lang#140772> due to the issue with host tools reported in <https://github.com/rust-lang/rust/issue/144533>. This reverts commits 508021a and d577b39. The decision was made in <rust-lang#144659 (comment)>. Tracking issue: <https://github.com/rust-lang/rust/issue/145435>
[beta] Revert #143031 and #140772 due to #144533 The decision was made in #144659 (comment). Tracking issue: #145435 r? jieyouxu try-job: dist-various-1
This is a temporary single-release workflow to create stage0 for these targets.
I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.
--enable-full-toolsfor whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory.rust-lang/compiler-team#877