Skip to content

std::process for fuchsia: updated to latest liblaunchpad #40139

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Mar 2, 2017

Conversation

tedsta
Copy link
Contributor

@tedsta tedsta commented Feb 28, 2017

Our liblaunchpad changed a bit and so fuchsia's std::process impl needs to change a bit.

@raphlinus

@rust-highfive
Copy link
Contributor

r? @alexcrichton

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

@@ -51,7 +51,7 @@ impl Command {
}

unsafe fn do_exec(&mut self, stdio: ChildPipes)
-> io::Result<(*mut launchpad_t, mx_handle_t)> {
-> io::Result< mx_handle_t> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Extra space here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

thanks for the catch

@raphlinus
Copy link
Contributor

This looks good to me, on reading the code. I'll build locally as well, just to make sure.

let mut process_handle: mx_handle_t = 0;
let mut err_msg: *const libc::c_char = ptr::null();
mx_cvt(launchpad_go(launchpad, &mut process_handle, &mut err_msg))?;
// TODO: See if we want to do something with that err_msg
Copy link
Contributor

Choose a reason for hiding this comment

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

The "tidy" linter didn't like this. It feels like a TODO to me, but if it wants FIXME, I suppose we should make it happy.

@alexcrichton
Copy link
Member

Looks great, thanks! r=me with the tidy failure fixed

@raphlinus
Copy link
Contributor

Confirm that Rust is functional again, xi editor builds and runs. I haven't deeply exercised process creation though.

@tedsta tedsta force-pushed the fuchsia_std_process_fix branch from e994eaf to a198b41 Compare February 28, 2017 18:26
@tedsta tedsta force-pushed the fuchsia_std_process_fix branch from a198b41 to 2123d6a Compare February 28, 2017 18:28
@tedsta
Copy link
Contributor Author

tedsta commented Feb 28, 2017

@bors r=alexcrichton tidy fixed

@raphlinus yeah I plan to write a bunch of unit tests for sys/fuchsia to give us some peace of mind.

@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Collaborator

bors commented Feb 28, 2017

📌 Commit 2123d6a has been approved by alexcrichton

@tedsta
Copy link
Contributor Author

tedsta commented Mar 1, 2017

Looks like some tests failed because of S3 outage yesterday. Is there a way I can trigger a rerun?

@alexcrichton
Copy link
Member

@tedsta oh this PR is in the queue which is the one that really matters, the Travis status on the PR itself is mostly just advisory currently

frewsxcv added a commit to frewsxcv/rust that referenced this pull request Mar 2, 2017
…lexcrichton

std::process for fuchsia: updated to latest liblaunchpad

Our liblaunchpad changed a bit and so fuchsia's std::process impl needs to change a bit.

@raphlinus
frewsxcv added a commit to frewsxcv/rust that referenced this pull request Mar 2, 2017
…lexcrichton

std::process for fuchsia: updated to latest liblaunchpad

Our liblaunchpad changed a bit and so fuchsia's std::process impl needs to change a bit.

@raphlinus
bors added a commit that referenced this pull request Mar 2, 2017
Rollup of 7 pull requests

- Successful merges: #39832, #40104, #40110, #40117, #40129, #40139, #40166
- Failed merges:
@bors bors merged commit 2123d6a into rust-lang:master Mar 2, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants