Navigation Menu

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

Fix some E-needstest issues. #45020

Merged
merged 1 commit into from Oct 8, 2017
Merged

Fix some E-needstest issues. #45020

merged 1 commit into from Oct 8, 2017

Conversation

MaloJaffre
Copy link
Contributor

Also ignore attr-on-trait test on stage-1 to keep ./x.py test --stage 1 successful.

Fixes #30355.
Fixes #33241.
Fixes #36400.
Fixes #37887.
Fixes #44578.

Also ignore `attr-on-trait` test on stage-1 to keep `./x.py test --stage 1` successful.

Fixes rust-lang#30355.
Fixes rust-lang#33241.
Fixes rust-lang#36400.
Fixes rust-lang#37887.
Fixes rust-lang#44578.
@rust-highfive
Copy link
Collaborator

r? @alexcrichton

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

Copy link
Contributor

@estebank estebank left a comment

Choose a reason for hiding this comment

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

r=me after verifying comment.

@@ -9,6 +9,7 @@
// except according to those terms.

// aux-build:attr-on-trait.rs
// ignore-stage1
Copy link
Contributor

Choose a reason for hiding this comment

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

why was this needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is the only test that fails on my machine (x86_64-unknown-linux-gnu with ./x.py test --stage 1), and because it is in run-pass-fulldeps, running it only in stage 2 doesn't seem a problem, because other tests in this directory are ignored on stage 1.

fn any<T>() -> T { unreachable!() }

#[rustc_error]
fn main() { //~ ERROR compilation successful
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you, instead of forcing the failure, make a run-pass test?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This test panics when running, because of the unreachable!().

Do you want me to move it to run-fail?

@shepmaster shepmaster added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Oct 6, 2017
@alexcrichton
Copy link
Member

@bors: r+

Thanks!

@bors
Copy link
Contributor

bors commented Oct 8, 2017

📌 Commit 7428806 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Oct 8, 2017

⌛ Testing commit 7428806 with merge ade0b01...

bors added a commit that referenced this pull request Oct 8, 2017
Fix some E-needstest issues.

Also ignore `attr-on-trait` test on stage-1 to keep `./x.py test --stage 1` successful.

Fixes #30355.
Fixes #33241.
Fixes #36400.
Fixes #37887.
Fixes #44578.
@bors
Copy link
Contributor

bors commented Oct 8, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing ade0b01 to master...

@bors bors merged commit 7428806 into rust-lang:master Oct 8, 2017
@MaloJaffre MaloJaffre deleted the needs-test branch October 8, 2017 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants