From: usa@... Date: 2019-04-29T19:14:17+00:00 Subject: [ruby-core:92482] [Ruby trunk Bug#15810] Windows spec failure - Process.ppid returns the process id of the parent of this process - ?? Issue #15810 has been updated by usa (Usaku NAKAMURA). Status changed from Open to Closed in `test-spec` target of make, `RUBY_EXE` constant in mspec is `RUNRUBY`. it means that the invoked ruby process is the grandchild of the invokee, not the child. so, this spec is never passed on Windows via `make test-spec`. ---------------------------------------- Bug #15810: Windows spec failure - Process.ppid returns the process id of the parent of this process - ?? https://bugs.ruby-lang.org/issues/15810#change-77828 * Author: MSP-Greg (Greg L) * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- Since being committed at 79671ec on 28-Apr, this spec has consistently failed: ``` Process.ppid returns the process id of the parent of this process FAILED Expected "11424\n" to equal "13044\n" C:/projects/ruby/spec/ruby/core/process/ppid_spec.rb:5:in `block (2 levels) in ' C:/projects/ruby/spec/ruby/core/process/ppid_spec.rb:3:in `' ``` But, testing it locally, both 'serial' & parallel, it passes. The test also passes at ruby/spec, and it passed with ruby-loco (which doesn't use make)... As to testing locally, if anyone wants to verify (on Windows), from the `spec/ruby` folder: ``` ../mspec/bin/mspec -rdevkit -j -T "--disable=gems" core ``` -- https://bugs.ruby-lang.org/ Unsubscribe: