-
Notifications
You must be signed in to change notification settings - Fork 143
Introduce force-inprocess feature #92
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
Conversation
☔ The latest upstream changes (presumably #93) made this pull request unmergeable. Please resolve the merge conflicts. |
What's up with this? Does the test failure point to an actual problem, or was that just some kind of Travis hiccup?... |
@antrik Sounds like an actual failure:
Will rebase and retry. |
@nox oh, I see what happened there: the condition for the fragmenting tests at https://github.com/servo/ipc-channel/blob/master/src/platform/test.rs#L207 needs to be adapted too, so these tests only run when actually using the BTW, I wonder whether there is some way to determine the backend to use in a single place, and store this in some kind of config variable that is used throughout the library, rather than having system-specific conditionals everywhere? (If there isn't, I'd consider that a serious shortcoming in Rust/Cargo...) |
@antrik Nice debugging, will disable these tests. |
} | ||
|
||
#[test] | ||
///XXXjdm Windows' libc doesn't include fork. |
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.
Keep the comment? r=me either way
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.
I think keeping the comment would be confusing: the multi-process tests actually can't work / don't make sense on platforms using the inprocess
implementation -- regardless of whether fork()
is available or not.
@bors-servo r+ |
📌 Commit 11615c3 has been approved by |
Introduce force-inprocess feature
@bors-servo r- |
@bors-servo r=Manishearth |
📌 Commit 11615c3 has been approved by |
💔 Test failed - status-travis |
@bors-servo r=Manishearth |
📌 Commit 02c7e75 has been approved by |
Introduce force-inprocess feature
💔 Test failed - status-travis |
@antrik Not running that test wasn't enough. |
src/platform/test.rs
Outdated
let (mut received_data, received_channels, received_shared_memory_regions) = | ||
super_rx.recv().unwrap(); | ||
// These tests only apply to platforms that need fragmentation. | ||
#[cfg(all(not(feature = "inprocess"), target_os = "linux"))] |
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.
It's force-inprocess
, not just inprocess
.
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.
Oh, I'm silly, thanks.
The other implementations take that, and the implementations should behave consistently.
Looks good :-) As you added the warning clean-ups, I guess it needs a new r+? Or is the previous one sufficient to cover this?... |
Just wanted you to take a last look. :) @bors-servo r=antrik |
📌 Commit 4d0369c has been approved by |
Introduce force-inprocess feature
💔 Test failed - status-appveyor |
@bors-servo retry |
Introduce force-inprocess feature
☀️ Test successful - status-appveyor, status-travis |
No description provided.