-
Notifications
You must be signed in to change notification settings - Fork 945
Demote deprecation #2162
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
Demote deprecation #2162
Conversation
The expect_not_stderr_ok() implementation incorrectly expected an error. This commit introduces expect_not_stderr_err() for that specific case, and fixes the test in expect_not_stderr_ok() Signed-off-by: Daniel Silverstone <[email protected]>
These tests actually wanted to be expect_not_stderr_err Signed-off-by: Daniel Silverstone <[email protected]>
So that we can send simple verbose messages at runtime, add a plain verbose notification message type. Signed-off-by: Daniel Silverstone <[email protected]>
We decided that the deprecation messages ought to be verbose messages (i.e. only in --verbose mode) rather than warnings. Fixes: rust-lang#2149 Signed-off-by: Daniel Silverstone <[email protected]>
Signed-off-by: Daniel Silverstone <[email protected]>
Somehow sometimes we still get ETXTBSY on Travis test suite runs This attempts to mitigate that a little more Signed-off-by: Daniel Silverstone <[email protected]>
I'd recommend reviewing this commit-by-commit because there's a bunch of cleanups in here too, to support the goal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Me from today thinks me from last night did an okay job.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Notification::PlainVerboseMessage
workaround is a bit annoying, but after asking @kinnison on other channels that seems like a necessary evil.
Looks good to me :)
This PR rearranges things a little to fix #2149 and tries to mitigate the ETXTBSY situation a little more.