-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Leave lld on beta a little bit more #145755
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
base: beta
Are you sure you want to change the base?
Conversation
- stable tests to ensure lld is not used - splitting beta (where lld is on) behavior from stable (where it is off)
Oh, so we should drop 1.90 release notes + blog mentioning this? We hadn't found much else to talk about in 1.90, so will need to do some digging... cc @rust-lang/release |
Do we really expect any meaningful feedback within the next 6 weeks from it being on beta? I have doubts that this will really have that effect, but I'll leave it to you to have the final call of course. |
I forgot to mention something: I'm not up-to-date on the discussion about the
I'm not sure. Maybe not as-is, but with a dedicated blog post motivating people to test their stuff on beta? |
On Ferrocene, we actually require folks to use |
I'm using nightly for running tests in the project just to use lld. It speeds up things for me. For the past 5 months, I have not seen any problems with it. |
@bors try |
Leave lld on beta a little bit more try-job: x86_64-gnu-stable try-job: dist-x86_64-linux try-job: x86_64-gnu
r? @Kobzol
As discussed, this leaves lld on beta a bit more, to allow for a longer period of testing:
(opening as draft as I wonder what tests we can make CI do to check the combination of tests.)
try-job: x86_64-gnu-stable
try-job: dist-x86_64-linux
try-job: x86_64-gnu