ruby.git/spec/ruby/core/process/times_spec.rb, branch v4.0.2 The Ruby Programming Language [DOC] State the precision of `Process.times` as platform-defined 2023-10-03T05:42:47+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2023-10-03T05:42:47+00:00 457971f4e243a76084d06ae840f4218b7a2062a3 Remove the bad example that can lead to misunderstanding as if this precision is defined in Ruby. 
Remove the bad example that can lead to misunderstanding as if this
precision is defined in Ruby.
Check by integer modulo instead of float string 2023-10-03T05:27:51+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2023-10-03T05:27:51+00:00 8be9138de2f9c6ce418f43ee55f5e6bce645bc28 






Check the precision of `getrusage` at runtime
2023-04-23T03:01:13+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-04-23T02:54:31+00:00

dafbaabc04e5a2d34045af78629a7249fd8c7481












Fix a guard of `Process.times`
2023-04-22T12:21:35+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-04-19T11:01:49+00:00

c5529aa5fc9cad4334bcb8ba36b96a9ea09c54e6

`GETRUSAGE_BASED_CLOCK_PROCESS_CPUTIME_ID` clock uses `getrusage`
always if available as the name states.  That is if it is implemented
`getrusage` is available, regardless microseconds in its results.





`GETRUSAGE_BASED_CLOCK_PROCESS_CPUTIME_ID` clock uses `getrusage`
always if available as the name states.  That is if it is implemented
`getrusage` is available, regardless microseconds in its results.







Fix an example of `Process.times`
2023-04-22T12:21:35+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-04-19T04:29:02+00:00

4cff7a92b8c97bb86dc1027b674a688f5182e302

Prior to commit 5806c54447439f2ba22892e4045e78dd80f96f0c, it was "at
least one result with precision beyond milliseconds (with none-zero
microseconds) should exist"; after this commit, "at least one result
should have zero microseconds".  This chance is lower than the
previous condition.





Prior to commit 5806c54447439f2ba22892e4045e78dd80f96f0c, it was "at
least one result with precision beyond milliseconds (with none-zero
microseconds) should exist"; after this commit, "at least one result
should have zero microseconds".  This chance is lower than the
previous condition.







Update to ruby/spec@9d69b95
2023-01-05T18:05:29+00:00

Benoit Daloze
eregontp@gmail.com

2023-01-05T18:05:29+00:00

bbf54ec334fe2edd7669a944d88d17efde49a412












Skip utime example with Intel C Compiler suite
2022-10-13T04:42:22+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2022-10-13T04:42:22+00:00

b734832883e3644af2527bd463de220a0b5794bc












Drop support for ruby 2.4 from ruby/spec
2020-04-01T06:36:20+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-02-08T10:43:27+00:00

826f44834fe11f3f9c52343443a15b6c83466889












Increase the number of Process.times attempts
2020-03-28T22:23:30+00:00

Takashi Kokubun
takashikkbn@gmail.com

2020-03-28T22:23:28+00:00

cf191872fdeade823b4c49b53ec9b28d66a5c402

CI of 5806c54447439f2ba22892e4045e78dd80f96f0c did not succeed
https://travis-ci.org/github/ruby/ruby/jobs/668072714





CI of 5806c54447439f2ba22892e4045e78dd80f96f0c did not succeed
https://travis-ci.org/github/ruby/ruby/jobs/668072714







Improve reliability of the Process.times spec
2020-03-28T13:39:01+00:00

Benoit Daloze
eregontp@gmail.com

2020-03-28T13:39:01+00:00

5806c54447439f2ba22892e4045e78dd80f96f0c