Skip to content

[beta] 1.46 beta #74323

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 3 commits into from
Jul 15, 2020
Merged

[beta] 1.46 beta #74323

merged 3 commits into from
Jul 15, 2020

Conversation

Mark-Simulacrum
Copy link
Member

@Mark-Simulacrum Mark-Simulacrum commented Jul 14, 2020

No description provided.

@Mark-Simulacrum
Copy link
Member Author

@bors r+ rollup=never p=20

@bors
Copy link
Collaborator

bors commented Jul 14, 2020

📌 Commit 2af7940 has been approved by Mark-Simulacrum

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Jul 14, 2020
@bors
Copy link
Collaborator

bors commented Jul 14, 2020

⌛ Testing commit 2af7940 with merge 07b17aaa944283e075e8e965d6954d26076c5823...

@Manishearth
Copy link
Member

@bors treeclosed=5

will continue to manually shepherd today

@bors
Copy link
Collaborator

bors commented Jul 14, 2020

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jul 14, 2020
@Manishearth
Copy link
Member

2020-07-14T14:05:10.4562495Z [RUSTC-TIMING] cargo_metadata test:false 8.008
2020-07-14T14:05:11.0796179Z �[0m�[1m�[38;5;9merror[E0635]�[0m�[0m�[1m: unknown feature `const_transmute`�[0m
2020-07-14T14:05:11.0796697Z �[0m  �[0m�[0m�[1m�[38;5;12m--> �[0m�[0m/cargo/registry/src/github.heygears.com-1285ae84e5963aae/rustc-ap-rustc_ast-664.0.0/lib.rs:13:12�[0m
2020-07-14T14:05:11.0797080Z �[0m   �[0m�[0m�[1m�[38;5;12m|�[0m
2020-07-14T14:05:11.0797433Z �[0m�[1m�[38;5;12m13�[0m�[0m �[0m�[0m�[1m�[38;5;12m| �[0m�[0m#![feature(const_transmute)]�[0m
2020-07-14T14:05:11.0798073Z �[0m   �[0m�[0m�[1m�[38;5;12m| �[0m�[0m           �[0m�[0m�[1m�[38;5;9m^^^^^^^^^^^^^^^�[0m
2020-07-14T14:05:11.0932281Z 

@Manishearth
Copy link
Member

I think we're going to have to wait for the rust ap stuff

@Manishearth
Copy link
Member

Once the ap stuff goes through would you mind updating this PR to include the clippy update? (currently in CI)

@Mark-Simulacrum
Copy link
Member Author

Oh right, I forgot we never fixed toolstate this cycle. Indeed this will need to wait for that and we'll just re-promote at that point (basically rebasing atop master) I imagine.

@bors
Copy link
Collaborator

bors commented Jul 14, 2020

⌛ Testing commit 2af7940 with merge 8309d7fda7313002b8b50cbbcbd3efe0827bf789...

@Manishearth
Copy link
Member

@bors r-

This had failed, no?

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 14, 2020
@Manishearth
Copy link
Member

homu seems to have gotten confused

@Manishearth
Copy link
Member

@bors yield

@Mark-Simulacrum
Copy link
Member Author

Mark-Simulacrum commented Jul 15, 2020

#72920 landed in the same rollup as the fix for the toolstate failures on rustfmt/RLS so we didn't note that the fix didn't actually fix things (since that PR introduced a regression, technically, in beta-week). I don't know that tooling could've detected it though -- I guess we should just not rollup toolstate-fixing PRs in beta week?

Anyway, I pushed up a dummy commit that just re-adds that const_transmute feature on a dummy function and seems to fix the build for RLS and rustfmt locally -- hopefully that's also the case on CI.

@bors r+ rollup=never p=20

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

📌 Commit 83b6d84 has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Jul 15, 2020
@bors
Copy link
Collaborator

bors commented Jul 15, 2020

💡 This pull request was already approved, no need to approve it again.

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

📌 Commit 83b6d84 has been approved by Mark-Simulacrum

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

⌛ Testing commit 83b6d84 with merge c20a0a4ad0888cb28993511e6f1e87ce622bd87c...

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jul 15, 2020
@Manishearth
Copy link
Member

     Running `build/x86_64-unknown-linux-gnu/stage2-tools/x86_64-unknown-linux-gnu/release/cargo-miri miri setup`
ERROR: the sysroot can't be built for the Beta channel. Switch to nightly.
fatal error: Failed to run xargo


command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "run" "--target" "x86_64-unknown-linux-gnu" "-Zbinary-dep-depinfo" "-j" "16" "--release" "--locked" "--color" "always" "--manifest-path" "/checkout/src/tools/miri/cargo-miri/Cargo.toml" "--features" "rustc-workspace-hack/all-static" "--" "miri" "setup"
expected success, got: exit code: 1


[TIMING] Miri { stage: 2, host: "x86_64-unknown-linux-gnu" } -- 33.283

2 command(s) did not execute successfully:

  - "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "test" "--target" "x86_64-unknown-linux-gnu" "-Zbinary-dep-depinfo" "-j" "16" "--release" "--locked" "--color" "always" "--manifest-path" "/checkout/src/tools/rustfmt/Cargo.toml" "--features" "rustc-workspace-hack/all-static"

  - "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "run" "--target" "x86_64-unknown-linux-gnu" "-Zbinary-dep-depinfo" "-j" "16" "--release" "--locked" "--color" "always" "--manifest-path" "/checkout/src/tools/miri/cargo-miri/Cargo.toml" "--features" "rustc-workspace-hack/all-static" "--" "miri" "setup"

failed to run: /checkout/obj/build/bootstrap/debug/bootstrap test --no-fail-fast src/doc/book src/doc/nomicon src/doc/reference src/doc/rust-by-example src/doc/embedded-book src/doc/edition-guide src/tools/rls src/tools/rustfmt src/tools/miri
Build completed unsuccessfully in 0:33:37

@Mark-Simulacrum
Copy link
Member Author

@bors r+ rollup=never p=20

Tools builder is passing on the PR at least.

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

📌 Commit dba515e has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 15, 2020
@mati865
Copy link
Contributor

mati865 commented Jul 15, 2020

Miri should not be built on beta and stable.

@Mark-Simulacrum
Copy link
Member Author

Miri failures are ignored -- we do currently try to build it, though. I'd be happy to take a patch that doesn't do so.

@mati865
Copy link
Contributor

mati865 commented Jul 15, 2020

That's what #73232 was supposed to fix 🤔

@Mark-Simulacrum
Copy link
Member Author

That's what #73232 was supposed to fix thinking

You're not wrong, but indeed the tools builder explicitly lists miri (

) so the defaults don't actually matter still -- only for x.py build for example will they affect things.

My guess is we can add some logic around (

let stage = self.stage;
that'll just refuse to test miri on stable/beta.

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

⌛ Testing commit dba515e with merge 139f54761d07ff14bbb3794bb687fa6de4227a19...

@mati865
Copy link
Contributor

mati865 commented Jul 15, 2020

I'll cc @RalfJung in case they want to continue work on #74323 (comment)

@RalfJung
Copy link
Member

I am not very familiar with that glue code. Wouldn't it make more sense to adjust

to not build nightly-only tools on non-nightly branches?

@Mark-Simulacrum
Copy link
Member Author

That would work too, I'm just less familiar with bash so would need to probably put in more effort (and we'd have a duplicate list of stable/unstable tools).

@RalfJung
Copy link
Member

OTOH it seems odd that an explicit request to build & test Miri would be ignored, even if the channel is stable.

Ideally the Python script that has the stable/unstable list would also drive x.py here, but I don't know how to arrange for that.

@Mark-Simulacrum
Copy link
Member Author

@bors retry - this failed forever ago https://github.com/rust-lang-ci/rust/runs/874170463

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

⌛ Testing commit dba515e with merge e51b714...

@bors
Copy link
Collaborator

bors commented Jul 15, 2020

☀️ Test successful - checks-actions, checks-azure
Approved by: Mark-Simulacrum
Pushing e51b714 to beta...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jul 15, 2020
@bors bors merged commit e51b714 into rust-lang:beta Jul 15, 2020
@RalfJung
Copy link
Member

How did this land now if Miri is failing?

@mati865
Copy link
Contributor

mati865 commented Jul 16, 2020

Miri fail is non fatal. It doesn't stop the build.

@RalfJung
Copy link
Member

Oh so the problem that came up here is that the build happened at all, not that the failure was a problem?

@mati865
Copy link
Contributor

mati865 commented Jul 16, 2020

I haven't checked the logs but something else must have failed.

@RalfJung
Copy link
Member

Okay I thought there was an actual problem here not just "we are running more tests than we should". Oh well.

Here's my partial attempt at fixing this: #74389. But I give up here, rustbuild is too hard to work on I am afraid and my Miri TODO list is already overflowing with other stuff. ;) Hopefully this is a start that someone else can build on, if anyone cares.

@cuviper cuviper added this to the 1.46 milestone May 2, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants