From: v.ondruch@... Date: 2016-11-08T14:13:22+00:00 Subject: [ruby-core:78051] [Ruby trunk Bug#12909] TestProcess#test_execopts_pgroup might fail Issue #12909 has been reported by Vit Ondruch. ---------------------------------------- Bug #12909: TestProcess#test_execopts_pgroup might fail https://bugs.ruby-lang.org/issues/12909 * Author: Vit Ondruch * Status: Open * Priority: Normal * Assignee: * ruby -v: ruby 2.4.0dev (2016-11-07 trunk 56664) [x86_64-linux] * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: REQUIRED ---------------------------------------- I am trying to build Ruby in container, using systemd-nspawn. In this environment, the TestProcess#test_execopts_pgroup test fails: ``` 1) Failure: TestProcess#test_execopts_pgroup [/builddir/build/BUILD/ruby-2.4.0-r56664/test/ruby/test_process.rb:184]: Errno::EPERM expected but nothing was raised. ``` Initially, I thought it must be something wrong, with mock (Fedora build env tool) or something with systemd-nspawn, but as it turns out, the test suite is probably rather naive. It assumes that 2 cannot be used as a pgid, but apparently it can. I'd say that this line [1] should be more dynamic, but I'm not really sure what it should be (actually it used to be 1, which works for my case, but it probably breaks for other scenarios). Please see [2] for the original report, analysis and explanation. [1]: https://github.com/ruby/ruby/blob/911f3d95033f54c0e02107873cbb4219e0ba377c/test/ruby/test_process.rb#L184 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1298228 -- https://bugs.ruby-lang.org/ Unsubscribe: