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

Rollup of 10 pull requests #21556

Closed
wants to merge 24 commits into from
Closed

Rollup of 10 pull requests #21556

wants to merge 24 commits into from

Conversation

quantheory and others added 24 commits January 15, 2015 13:49
… directory's name, and remove the directory after a successful test.
Also makes errorck.py and tidy.py compatible with Python 3.
While trying to experiment with changes for some other issues, I noticed that the test for rust-lang#15149 was failing because I have `/tmp` mounted as `noexec` on my Linux box, and that test tries to run out of a temporary directory. This may not be the most common case, but it's not rare by any means, because executing from a world-writable directory is a security problem. (For this reason, some kernel options/mods such as grsecurity also can prevent this on Linux.) I instead copy the executable to a directory created in the build tree, following the example of the `process-spawn-with-unicode-params` test.

After I made that change, I noticed that I'd made a mistake, but the test was still passing, because the "parent" process was not actually checking the status of the "child" process, meaning that the assertion in the child could never cause the overall test to fail. (I don't know if this has always been the case, or if it has something to do with either Windows or a change in the semantics of `spawn`.) So I fixed the test so that it would fail correctly, then fixed my original mistake so that it would pass again.

The one big problem with this is that I haven't set up any machines of my own so that I can build on Windows, which is the platform this test was targeted at in the first place! That might take a while to address on my end. So I need someone else to check this on Windows.
…=alexcrichton

Fix for `error: functions used as tests must have signature fn() -> ()` and `error: functions used as benches must have signature `fn(&mut Bencher) -> ()` in case of explicit return type declaration.
Fixes rust-lang#19759 

I'm not going to bother to do more than this, as it'll end up getting re-done as part of the reference work, but at least it's correct now.
Also makes `errorck.py` and `tidy.py` compatible with Python 3.
@rust-highfive
Copy link
Collaborator

r? @brson

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

@brson
Copy link
Contributor

brson commented Jan 23, 2015

@bors: r+ fef3b6d p=1

@bors
Copy link
Contributor

bors commented Jan 23, 2015

⌛ Testing commit fef3b6d with merge fc297e3...

@bors
Copy link
Contributor

bors commented Jan 23, 2015

💔 Test failed - auto-mac-64-opt

@alexcrichton
Copy link
Member

@bors: retry

@bors
Copy link
Contributor

bors commented Jan 23, 2015

⌛ Testing commit fef3b6d with merge 540118d...

@bors
Copy link
Contributor

bors commented Jan 23, 2015

💔 Test failed - auto-mac-64-opt

@flaper87
Copy link
Contributor Author

@alexcrichton retry ? :/

@barosl
Copy link
Contributor

barosl commented Jan 24, 2015

@flaper87 The test failure is legit, so you should add a commit that addresses https://github.com/rust-lang/rust/pull/21529/files#r23487891 to this PR instead of just retrying it.

Or we can wait for @tshepang to resolve this issue. But in that case again, you should open a new rollup PR, so either way there needs to be some manual intervention.

@barosl
Copy link
Contributor

barosl commented Jan 24, 2015

But I also think it would be better to open a new one anyways because we have three more PRs to roll up now...

@tshepang
Copy link
Member

@barosl I have fixed the issue. Sorry for the pain :(

@flaper87
Copy link
Contributor Author

@barosl oh mmh, it was late and I mistakenly assumed the issue was spurious because the job failing was the same. I'll re-open a new rollup.

@flaper87 flaper87 closed this Jan 24, 2015
@Centril Centril added the rollup A PR which is a rollup label Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup
Projects
None yet
Development

Successfully merging this pull request may close these issues.