-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
std: Fix usage of SOCK_CLOEXEC #34946
Conversation
This code path was intended to only get executed on Linux, but unfortunately the `cfg!` was malformed so it actually never got executed.
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ |
📌 Commit 15cd5a1 has been approved by |
⌛ Testing commit 15cd5a1 with merge 4b0371c... |
💔 Test failed - auto-linux-64-cargotest |
@bors: retry On Wed, Jul 20, 2016 at 6:01 PM, bors notifications@github.com wrote:
|
⌛ Testing commit 15cd5a1 with merge 4b24e08... |
💔 Test failed - auto-win-msvc-64-opt-mir |
@bors: retry On Thu, Jul 21, 2016 at 12:39 PM, bors notifications@github.com wrote:
|
⌛ Testing commit 15cd5a1 with merge 1054428... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
@bors: retry On Fri, Jul 22, 2016 at 4:17 PM, bors notifications@github.com wrote:
|
std: Fix usage of SOCK_CLOEXEC This code path was intended to only get executed on Linux, but unfortunately the `cfg!` was malformed so it actually never got executed.
💔 Test failed - auto-linux-64-x-android-t |
@bors: retry |
⌛ Testing commit 15cd5a1 with merge d33473b... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
@bors: retry On Sun, Jul 24, 2016 at 10:47 PM, bors notifications@github.com wrote:
|
@bors: retry |
⌛ Testing commit 15cd5a1 with merge 65b403a... |
💔 Test failed - auto-win-gnu-32-opt |
@bors: retry On Mon, Jul 25, 2016 at 2:59 PM, bors notifications@github.com wrote:
|
⌛ Testing commit 15cd5a1 with merge d510024... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
@bors: retry On Tue, Jul 26, 2016 at 3:20 AM, bors notifications@github.com wrote:
|
std: Fix usage of SOCK_CLOEXEC This code path was intended to only get executed on Linux, but unfortunately the `cfg!` was malformed so it actually never got executed.
This code path was intended to only get executed on Linux, but unfortunately the
cfg!
was malformed so it actually never got executed.