summaryrefslogtreecommitdiff
path: root/spec/ruby/core/process/clock_getres_spec.rb
AgeCommit message (Collapse)Author
2020-05-03spec/ruby/core/process/clock_getres_spec.rb: lax the resolution limitYusuke Endoh
Android is Linux, but the clock resolution is 10 milliseconds. I think that 1 microsecond is too strict for embedded environment. This change laxes the limit to 10 milliseconds.
2020-05-02Update to ruby/spec@d394dfdBenoit Daloze
2020-04-19Skip Process#clock_getres specs on AndroidYusuke Endoh
... just like AIX and OpenBSD.
2020-03-28Remove Process.clock_getres "matches the resolution in practice" specsBenoit Daloze
* Almost all platforms return incorrect values for Process.clock_getres, it should be removed: https://bugs.ruby-lang.org/issues/16740
2020-03-24Show failed timesNobuyoshi Nakada
2020-03-23Try to avoid random failures on clock_getres_spec.rbTakashi Kokubun
This spec fails too often https://github.com/ruby/ruby/runs/529546249 https://github.com/ruby/ruby/runs/524933256
2020-02-13spec/ruby/core/process/clock_getres_spec.rb: skip on AndroidYusuke Endoh
in the same way as FreeBSD and OpenBSD. I guess that the spec makes too strong assumption.
2019-11-30Update to ruby/spec@4eec3dcBenoit Daloze
2019-06-06Make specs pass on OpenBSDJeremy Evans
Skip Process clockres specs that don't work on either FreeBSD or Solaris/AIX in addition to OpenBSD. Run most current String#crypt specs on non-OpenBSD, and add a new set of crypt specs for OpenBSD, which support bcrypt but not DES in crypt(3). Use @server.connect_address instead of @server.getsockname in some socket tests, as OpenBSD does not treat connection to all zero IPv4 or IPv6 addresses as connection to localhost. When trying to connect using UDP on an unsupported address family, allow Errno::EPROTONOSUPPORT in addition to Errno::EAFNOSUPPORT, as OpenBSD raises the former.
2019-05-24Add notes for the Process#clock_getres specBenoit Daloze
2019-05-24Only exclude the failing clocks for Process.clock_getres specs on AIXBenoit Daloze
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20190522T103301Z.fail.html.gz
2019-05-24Skip the Process.clock_getres spec on AIXYusuke Endoh
https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20190522T103301Z.fail.html.gz
2019-05-20Move exclusion for Hyper-V next to other skipped constantsBenoit Daloze
2019-05-20skip a test for CLOCK_MONOTONIC_RAW.Koichi Sasada
On my Linux guest machine on Hyper-V, I got an error. Process.clock_gettime(CLOCK_MONOTONIC_RAW, :nanosecond) returns like: ... 875573945119100 875573945119600 ... even if `Process.clock_getres(value, :nanosecond)` returns 1. So I simply skip this test for CLOCK_MONOTONIC_RAW.
2019-04-28Move the check for CentOS CLOCK_MONOTONIC_RAW next to othersBenoit Daloze
* Fixes "No behavior expectation was found in the example" * https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos6/ruby-trunk/log/20190428T093004Z.fail.html.gz
2019-04-28Skip CLOCK_UPTIME_RAW_APPROX since it seems less precise than advertised on ↵Benoit Daloze
macOS * See https://travis-ci.org/ruby/ruby/jobs/525595997
2019-04-28Exclude failing Process.clock_getres specs on AIXBenoit Daloze
2019-04-28Skip problematic Process.clock_getres specs on ARMBenoit Daloze
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-trunk/log/20190428T051708Z.fail.html.gz * https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-ad7f67/ruby-trunk/log/20190428T045405Z.fail.html.gz
2019-04-28Workaround a CentOS bug in Process.clock_getres specsBenoit Daloze
2019-04-28Skip the entire Process.clock_getres spec on FreeBSDBenoit Daloze
* Clocks don't match the reported precision. * https://rubyci.org/logs/rubyci.s3.amazonaws.com/freebsd11zfs/ruby-trunk/log/20190428T093003Z.fail.html.gz
2019-04-27Some Solaris versions seem to only provide millisecond accuracy for ↵Benoit Daloze
CLOCK_REALTIME * https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20190427T182404Z.fail.html.gz
2019-04-27Skip clock_getres spec on BSDBenoit Daloze
* clock_getres() seems to be incorrect on BSD: https://rubyci.org/logs/rubyci.s3.amazonaws.com/freebsd11zfs/ruby-trunk/log/20190427T183003Z.fail.html.gz
2019-04-27Update to ruby/spec@15c9619Benoit Daloze