mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
d069339110
spec/ruby/core/process/clock_getres_spec.rb: skip on Android in the same way as FreeBSD and OpenBSD. I guess that the spec makes too strong assumption. Try to avoid random failures on clock_getres_spec.rb This spec fails too often https://github.com/ruby/ruby/runs/529546249 https://github.com/ruby/ruby/runs/524933256 Show failed times Remove Process.clock_getres "matches the resolution in practice" specs * Almost all platforms return incorrect values for Process.clock_getres, it should be removed: https://bugs.ruby-lang.org/issues/16740 Skip Process#clock_getres specs on Android ... just like AIX and OpenBSD. Update to ruby/spec@d394dfd spec/ruby/core/process/clock_getres_spec.rb: lax the resolution limit 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. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| gid | ||
| status | ||
| sys | ||
| uid | ||
| abort_spec.rb | ||
| clock_getres_spec.rb | ||
| clock_gettime_spec.rb | ||
| constants_spec.rb | ||
| daemon_spec.rb | ||
| detach_spec.rb | ||
| egid_spec.rb | ||
| euid_spec.rb | ||
| exec_spec.rb | ||
| exit_spec.rb | ||
| fork_spec.rb | ||
| getpgid_spec.rb | ||
| getpgrp_spec.rb | ||
| getpriority_spec.rb | ||
| getrlimit_spec.rb | ||
| gid_spec.rb | ||
| groups_spec.rb | ||
| initgroups_spec.rb | ||
| kill_spec.rb | ||
| last_status_spec.rb | ||
| maxgroups_spec.rb | ||
| pid_spec.rb | ||
| ppid_spec.rb | ||
| set_proctitle_spec.rb | ||
| setpgid_spec.rb | ||
| setpgrp_spec.rb | ||
| setpriority_spec.rb | ||
| setrlimit_spec.rb | ||
| setsid_spec.rb | ||
| spawn_spec.rb | ||
| times_spec.rb | ||
| uid_spec.rb | ||
| wait2_spec.rb | ||
| wait_spec.rb | ||
| waitall_spec.rb | ||
| waitpid2_spec.rb | ||
| waitpid_spec.rb | ||