Issue #10202 has been updated by Eric Wong.


 Thanks for the confirmation! r47526 removes CLOCK_MONOTONIC_RAW.
 
 r47526 | normal | 2014-09-11 08:09:07 +0000 (Thu, 11 Sep 2014) | 14 lines
 
 lib/benchmark.rb: remove CLOCK_MONOTONIC_RAW support
 
 In addition to being unaffected by _offset_ correction,
 CLOCK_MONOTONIC_RAW is also unaffected by _frequency_ correction,
 making it unsuitable for measuring real time on systems where the
 clock is always running too fast or slow.
 
 CLOCK_MONOTONIC (without _RAW) is the correct clock, as it is unaffected
 by _offset_ correction (due to human error or battery replacement), but
 still takes _frequency_ correction into account for clocks which
 consistently run too fast or slow.
 
 Thanks to Vt Ondruch for reporting the issue on ARM [Bug #10202]

----------------------------------------
Bug #10202: TestBenchmark#test_realtime_output breaks on ARM
https://bugs.ruby-lang.org/issues/10202#change-48845

* Author: Vit Ondruch
* Status: Closed
* Priority: Normal
* Assignee: Akira Tanaka
* Category: 
* Target version: 
* ruby -v: ruby 2.2.0dev (2014-09-03 trunk 47372) [armv7hl-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
I observe following error on ARM:

~~~
  3) Failure:
TestBenchmark#test_realtime_output [/builddir/build/BUILD/ruby-2.2.0-r47372/test/benchmark/test_benchmark.rb:159]:
Expected 1.0 to be < 0.999977873172611.
~~~

It seems to be introduced by r47360. Reverting the commit makes test suite to pass once again.



-- 
https://bugs.ruby-lang.org/