From: merch-redmine@... Date: 2021-03-18T00:06:42+00:00 Subject: [ruby-core:102910] [Ruby master Bug#16608] ConditionVariable#wait should return false when timeout exceeded Issue #16608 has been updated by jeremyevans0 (Jeremy Evans). @matz agreed to change the return value of Mutex#sleep at the last developer meeting. However, that breaks a Mutex_m test: https://github.com/ruby/ruby/pull/4256/checks?check_run_id=2135513377#step:15:1295 So the Mutex_m test needs to be fixed first, a new release needs to be made, and the bundled gems need to be updated, before the Mutex#sleep change can be merged. ---------------------------------------- Bug #16608: ConditionVariable#wait should return false when timeout exceeded https://bugs.ruby-lang.org/issues/16608#change-90974 * Author: shugo (Shugo Maeda) * Status: Assigned * Priority: Normal * Assignee: nobu (Nobuyoshi Nakada) * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- The following program prints `false` on Ruby 1.8, but `true` on Ruby 1.9 or later. ``` require "monitor" m = Monitor.new c = m.new_cond m.synchronize { p c.wait(0.1) } ``` However, it's not critical because most programs check the condition after wait. -- https://bugs.ruby-lang.org/ Unsubscribe: