From fa47aa3aca08ad4e75c8aa024d2b21d349c44326 Mon Sep 17 00:00:00 2001 From: "Joshua M. Clulow" Date: Tue, 8 Dec 2020 08:59:40 +0000 Subject: [PATCH] ignore tcp_shutdown_client_both_close_event failure on illumos At present, is_write_closed() does not appear to be true on the event that fires after shutdown() is called. There is already a similar gag for the tcp_shutdown_client_write_close_event test, so add one here for now. When support for the native illumos "event ports" polling mechanism is added, to replace the use of epoll emulation, this can be revisted. --- tests/tcp_stream.rs | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/tcp_stream.rs b/tests/tcp_stream.rs index 4722b7589..cf333dbc9 100644 --- a/tests/tcp_stream.rs +++ b/tests/tcp_stream.rs @@ -659,6 +659,10 @@ fn tcp_reset_close_event() { windows, ignore = "fails on Windows; client close events are not found" )] +#[cfg_attr( + any(target_os = "illumos"), + ignore = "fails; client write_closed events are not found" +)] fn tcp_shutdown_client_both_close_event() { let (mut poll, mut events) = init_with_poll(); let barrier = Arc::new(Barrier::new(2));