ruby.git/spec/ruby/core/process, branch ruby_2_7

merge revision(s) ed549f80b645aafd62376f65c3a27b66bafa2a38,eff0c5bf2ad47d10a440c5211be5eddb3bbf4028,f6b6a7ad345c50eeb3f7206ceabdf41ba94b7d85,5b48686691c2443d8d7113e593494c4d9302da0e,2af4c1fc5b19fc96203c2d7e917e689510d3527e,c9213aa864fb8527388679c21f1ea8ce129e2f1a,224f29c8e92094af10bc666c474b81a3545d6adf:

2020-12-31T09:34:09+00:00

	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.

Make more attempts to check for the precision of Process.times

2019-12-02T20:23:10+00:00

* Process.clock_getres specs use 10_000 but that's quite slow for
  the Process.times spec.

Fix random failure on getusage-missing environments

2019-12-02T08:17:41+00:00

`* 1e6` makes a spurious result about floating point number's precision.

```
irb(main)[01:0]> 16.028
=> 16.028
irb(main)[02:0]> (16.028 * 1e6)
=> 16027999.999999998
```

Debug random failure of ruby-spec on ci.rvm.jp

2019-12-02T07:23:40+00:00

Skip if getrusage is not supported

2019-11-30T21:29:01+00:00

1243255c3a36433041012b6107a5ac48658a0895 broke ci.rvm.jp tests like
http://ci.rvm.jp/results/trunk_clang_39@silicon-docker/2445098.

253232c028a5565dbeecc05fab5e81b35ab58bcc works only if getrusage is supported.

Update to ruby/spec@4eec3dc

2019-11-30T20:26:52+00:00

Exclude some clocks on armv8 too

2019-11-06T22:10:15+00:00

* See https://bugs.ruby-lang.org/issues/16234#note-16

Fix spawn_spec.rb for Travis arm64 environment.

2019-11-06T17:08:37+00:00

The process group id (/proc/[pid]/stat 5th field) is 0
in the Travis arm64 environment.

This is a case where it is available.

$ cat /proc/4543/stat
4543 (ruby) S 4525 4525 1384 34818 4525 4194304 37443 1754841 0 0 366 105 2291 391 20 0 3 0 1381328 1428127744 11475 18446744073709551615 94195983785984 94195986670225 140728933833312 0 0 0 0 0 1107394127 0 0 0 17 2 0 0 1 0 0 94195987686512 94195987708942 94196017770496 140728933835483 140728933835595 140728933835595 140728933842904 0

This is a case where it is not available in Travis arm64 environment.

$ cat /proc/19179/stat
19179 (ruby) S 19160 0 0 0 -1 4194560 37618 1710547 313 163 770 665 5206 1439 20 0 2 0 17529566 1196347392 10319 18446744073709551615 187650811428864 187650815023116 281474602721280 0 0 0 0 4096 1107390031 0 0 0 17 22 0 0 0 0 0 187650815091456 187650815114064 187651414974464 281474602725080 281474602725211 281474602725211 281474602729420 0

See "man proc" for detail.

Make test-all and test-spec runnable on Android

2019-09-09T11:24:03+00:00

Calling some syscall functions such as Dir.chroot causes SIGSYS instead
of EPERM on Android.
This change skips all tests that stops the test-suite run.

armv7l and armv7l are the same platform, generalize to armv7

2019-09-07T10:53:47+00:00

[Bug #16007]