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

Windows: failing unit tests in libstd\rt\uv\file.rs #8814

Closed
vadimcn opened this issue Aug 28, 2013 · 0 comments
Closed

Windows: failing unit tests in libstd\rt\uv\file.rs #8814

vadimcn opened this issue Aug 28, 2013 · 0 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows A-testsuite Area: The testsuite used to check the correctness of rustc O-windows Operating system: Windows

Comments

@vadimcn
Copy link
Contributor

vadimcn commented Aug 28, 2013

file_test_full_simple
failed in non-task context at 'assertion failed: uverr.is_none()', C:\Rust\src\libstd\rt\uv\file.rs:312
file_test_full_simple_sync
failed in non-task context at 'assertion failed: result.is_ok()', C:\Rust\src\libstd\rt\uv\file.rs:374

@bors bors closed this as completed in 6d9c399 Sep 16, 2013
xFrednet pushed a commit to xFrednet/rust that referenced this issue May 21, 2022
…vec-init, r=xFrednet

add suggestions to rc_clone_in_vec_init

A followup to rust-lang/rust-clippy#8769
I also switch the order of the 2 suggestions, since the loop initialization one is probably the common case.

`@xFrednet` I'm not letting you guys rest for a minute 😅
changelog: add suggestions to [`rc_clone_in_vec_init`]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows A-testsuite Area: The testsuite used to check the correctness of rustc O-windows Operating system: Windows
Projects
None yet
Development

No branches or pull requests

1 participant