Skip to content

sync::mpsc::select::test::stress is flaky on Windows #22771

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

Closed
klutzy opened this issue Feb 24, 2015 · 2 comments
Closed

sync::mpsc::select::test::stress is flaky on Windows #22771

klutzy opened this issue Feb 24, 2015 · 2 comments
Labels
O-windows Operating system: Windows

Comments

@klutzy
Copy link
Contributor

klutzy commented Feb 24, 2015

Using Rust rev dcc6ce2, stage1 stdtest.

$ ./stdtest-x86_64-pc-windows-gnu.exe sync::mpsc::select::test::

thread '<unnamed>' panicked at 'assertion failed: i % 2 == 1 && i == i2.unwrap()',
C:\home\stone\rust\src\libstd\sync\mpsc\select.rs:493

test sync::mpsc::select::test::stress ... FAILED

cc #22628, #22710

@sanxiyn sanxiyn added the O-windows Operating system: Windows label Feb 24, 2015
@klutzy
Copy link
Contributor Author

klutzy commented Feb 25, 2015

Note that there are other channel() tests which are flaky as well.

thread '<unnamed>' panicked at 'assertion failed: `(left == right) && (right == left)`
(left: `2`, right: `4`)', C:\home\stone\rust\src\libstd\sync\mpsc\mod.rs:1494

test sync::mpsc::test::test_recv_iter_break ... FAILED

My hypothesis is channel() is flaky therefore Receiver.recv() may hang even if Sender.send() called.

@klutzy
Copy link
Contributor Author

klutzy commented Mar 6, 2016

Not producible anymore. (see #22710)

@klutzy klutzy closed this as completed Mar 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-windows Operating system: Windows
Projects
None yet
Development

No branches or pull requests

2 participants