summaryrefslogtreecommitdiff
path: root/spec/ruby/core/process
AgeCommit message (Collapse)Author
2019-11-06Exclude some clocks on armv8 tooBenoit Daloze
* See https://bugs.ruby-lang.org/issues/16234#note-16
2019-11-06Fix spawn_spec.rb for Travis arm64 environment.Jun Aruga
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. Notes: Merged: https://github.com/ruby/ruby/pull/2653
2019-09-09Make test-all and test-spec runnable on AndroidYusuke Endoh
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.
2019-09-07armv7l and armv7l are the same platform, generalize to armv7Benoit Daloze
[Bug #16007]
2019-07-27Update to ruby/spec@875a09eBenoit Daloze
2019-07-16Removed twisted testsNobuyoshi Nakada
Why does only Process.daemon have these tests?
2019-06-27Update to ruby/spec@8d74d49Benoit 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-20Remove redundant ignore rule for Process#clock_getres specsBenoit Daloze
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-30Skip the spec on Windows because RUBY_EXE is RUNRUBY and it calls ruby as ↵NAKAMURA Usaku
grandchild
2019-04-28CLOCK_MONOTONIC_RAW_APPROX seems less precise than advertised on macOSBenoit Daloze
* https://travis-ci.org/ruby/ruby/builds/525651487
2019-04-28Update to ruby/spec@7de852dBenoit Daloze
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-28Add missing platform guardBenoit 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-28Refactor logic in Process.clock_gettime specBenoit Daloze
2019-04-28Fix typo in specBenoit 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
2019-02-07Update to ruby/spec@6cf8ebeeregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67030 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-01-20Update to ruby/spec@35a9fbaeregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66888 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-30Exclude Solaris in Process.clock_gettime specseregon
* It declares clocks which are invalid for clock_gettime(), which I consider OS bug. * I want to keep testing all declared clocks on other platforms. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66657 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-30Revert "clock_gettime_spec.rb: exclude invalid clocks for Solaris"eregon
* This reverts commit a7edd05f7dca44f56fd72d7bcc232e1b27df0eb3. * I prefer to exclude Solaris, I want to keep testing these clocks on Linux/macOS. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66655 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-30clock_gettime_spec.rb: exclude invalid clocks for Solarisk0kubun
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10x/ruby-trunk/log/20181230T041806Z.fail.html.gz https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20181230T042407Z.fail.html.gz https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11s/ruby-trunk/log/20181230T032505Z.fail.html.gz https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris11s-sunc/ruby-trunk/log/20181230T022505Z.fail.html.gz git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66650 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-30Update to ruby/spec@2d89e48eregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66645 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Skip specs on AIX as it doesn't have /dev/fderegon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66643 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Reenable spec on Solaris to find out which clocks fail on Solariseregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66642 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Exclude CLOCKs which require special permissions in Process.clock_gettime specseregon
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-ad7f67/ruby-trunk/log/20181229T135406Z.fail.html.gz * https://rubyci.org/logs/rubyci.s3.amazonaws.com/rhel_zlinux/ruby-trunk/log/20181229T143303Z.fail.html.gz git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66641 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Reenable spec on Linux to find out which clocks fail on RHELeregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66636 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Refactor Process.clock_gettime spec to give more information when it failseregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66635 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29clock_gettime_spec.rb: add more platform guards for RubyCIk0kubun
`Errno::EINVAL: Invalid argument - clock_gettime` could occur even on Linux. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66633 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29spawn_spec.rb: add missing platform guardk0kubun
this exists for `context "when passed close_others: false" do`, but this seems to be missing for `context "when passed close_others: true"`. And this seems to hang forever on Windows since r66622. https://ci.appveyor.com/project/ruby/ruby/builds/21277729 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66627 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29clock_gettime_spec.rb: skip a new spec broken on solarisk0kubun
introduced in r66622, but this does not succeed on Solaris https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20181229T002409Z.fail.html.gz git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66624 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Update to ruby/spec@c8b36c4eregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66623 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-29Update to ruby/spec@944ea57eregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66622 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-12-26spec/ruby/core/process/setpriority_spec.rb: allow to run under dockermame
Docker container is not always able to lower the nice value even if the euid is a root. It depends upon the configuration of docker which cannot check from the container itself. This change does check it by actually trying to lower the value first. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66570 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-27Update to ruby/spec@cdd6ff7eregon
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66041 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-18Always set autoclose=false for IO.for_fd fdseregon
* I believe this should be default behavior, see [Feature #2250]. * Now make test-spec MSPECOPT='-R100 spec/ruby/library/socket' works fine. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64454 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-10process.c: fix rubyspec of Process.groupsmrkn
getgroups(2) may return a GID list that includes duplicated GIDs. The behavior is totaly depends on what OS is used. This commit fixes the example of Process.groups so that the example is independent of this OS-dependent features. Additonaly, this commit adds the description of such system-dependent characteristics of Process.groups. [ruby-dev:50603] [Bug #14969] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64265 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-07-07process.c (rb_f_exec): pause MJIT before replacing processnormal
Non-parallel "make test-spec" caused spec/ruby/core/process/wait2_spec.rb failures because mspec uses "exec" in single-process mode, so there's no chance the post-exec state could know about the MJIT child process from its pre-exec state. [ruby-core:87846] [Bug #14867] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63877 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-20 11:00:14 +0000