Skip to content
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

Stabilize allow_fail flag test feature #46501

Conversation

GuillaumeGomez
Copy link
Member

Fixes #46488.

@rust-highfive
Copy link
Collaborator

r? @michaelwoerister

(rust_highfive has picked a reviewer for you, use r? to override)

@GuillaumeGomez GuillaumeGomez force-pushed the allow-fail-stabilization branch 2 times, most recently from d336766 to c146537 Compare December 4, 2017 21:29
@kennytm kennytm added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 5, 2017
@bors
Copy link
Contributor

bors commented Dec 7, 2017

☔ The latest upstream changes (presumably #46528) made this pull request unmergeable. Please resolve the merge conflicts.

@GuillaumeGomez
Copy link
Member Author

Rebased.

@carols10cents
Copy link
Member

review ping for you @michaelwoerister !

@michaelwoerister
Copy link
Member

I don't really know about this.

r? @nrc

@nrc nrc added I-nominated S-waiting-on-team Status: Awaiting decision from the relevant subteam (see the T-<team> label). T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 15, 2017
@nrc
Copy link
Member

nrc commented Dec 15, 2017

I think this needs some discussion before stabilisation - there was quite a lot of discussion on the original PR about whether this was a good idea or not, and I don't see any indication that this feature has proved itself in the meantime. Let's discuss at the next dev-tools meeting.

@kennytm
Copy link
Member

kennytm commented Jan 10, 2018

Triage ping @rust-lang/dev-tools! Has this been discussed and is there a conclusion on this PR?

@@ -519,6 +516,8 @@ declare_features! (
// Allows the sysV64 ABI to be specified on all platforms
// instead of just the platforms on which it is the C ABI
(accepted, abi_sysv64, "1.24.0", Some(36167)),
// Allows a test to fail without failing the whole suite
(accepted, allow_fail, "1.23.0", Some(42219)),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a quick note: this should be ≥1.25.0 by now

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh indeed!

@GuillaumeGomez
Copy link
Member Author

@kennytm: The meeting is tomorrow so I hope we'll discuss it at this time.

@nrc
Copy link
Member

nrc commented Jan 18, 2018

Discussed at dev-tools meeting, we plan not to stabilise this feature

@GuillaumeGomez GuillaumeGomez deleted the allow-fail-stabilization branch January 19, 2018 10:04
@apiraino apiraino removed the S-waiting-on-team Status: Awaiting decision from the relevant subteam (see the T-<team> label). label May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stabilize allow_fail test flag
9 participants