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
This comment has been minimized.
This comment has been minimized.
|
as it seems @Noratrieb and @petrochenkov disagree that this is worthwhile, let's not bother, and announce that people should test on beta to prepare for next month's release |
I've opened a PR for that in rust-lang/blog.rust-lang.org#1682 |
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