Allow nightly builds to fail#2131
Conversation
83bd914 to
d1cbfa3
Compare
If a nightly build fails a warning instead of an error is shown in the build console
d1cbfa3 to
33d0188
Compare
0e0baf6 to
56a0adf
Compare
|
Hopefully this makes #2117 obsolete. |
|
Would be great if azure pipelines would report that there were warnings. They are shown in the build status over there, but I'm not sure why they are not reported to github |
|
Ugh, |
|
This PR seems good to me so we can merge this now then we can go to #2108, or this can also include its changes (or add |
|
Can we go? Or should we wait for another review? |
|
I would like to hear at least another opinion about the use of |
|
So IIUC, the cap-lints part is to make depreciation warning stay as warnings even with a |
Yes, but only for the nightly compiler. It is basically meant as a poor mans |
|
That would not work on the event of something erroring for real then ? That's kind of a bummer because a dependency might be broken on nightly for some reasons and we don't want that to make the build red in that case either |
|
Right, if we want to prevent that we would need to set the this return here to true. I'm not sure if we really want to do that, because ~all of our breakage from the last time was basically rustc introducing some new lint/deprecation/… in nightly. |
|
Yeah but I've seen stuff erroring due to errors in dependencies in the past on other projects. I guess this is not common enough to worry about especially since it's fixed quickly most of the time. I wish rustc would add a cfg for nightly compilers so we could do I guess this is fine then 👍 |
If a nightly build fails a warning instead of an error is shown in the
build console