29 Apr '13, 8am

さっきのAsyncWatcherのテスト,3年以上前のテストかー >

I actually found this bug while chasing down some weird behavior with IO#read under 1.8 (which does not affect 1.9). I was unable to reproduce what was happening inside Rainbows![1] in an isolated test case, but I found another failure case for this test. [1] - which does not share AsyncWatcher across fork, but does handle a lot of signals. >From e2ab2b774ce6431519a42ac5b831708f14069801 Mon Sep 17 00:00:00 2001 From: Eric Wong <normalperson at yhbt.net > Date: Thu, 26 Nov 2009 18:11:17 -0800 Subject: [PATCH] async_watcher: do not trigger on spurious wakeups Also included is a convoluted test case that is able to reliably reproduce the failure on both a UP and SMP Linux 2.6 machines without this change. --- lib/rev/async_watcher.rb | 7 ++++- spec/async_watcher_spec.rb | 57 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 63 insertions(+), 1 deletions(-) create ...

Full article: http://rubyforge.org/pipermail/rev-talk/2009-November/000...

Tweets