[ruby-core:92514] [Ruby trunk Bug#15810] Windows spec failure - Process.ppid returns the process id of the parent of this process - ??

[eregontp@gmail.com]

Issue #15810 has been updated by Eregon (Benoit Daloze).


Would it be possible to use execve() in RUNRUBY, such that RUNRUBY and the actual ruby process have the same PID, or is that not available on Windows?

----------------------------------------
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-77876

* 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 <top (required)>'
C:/projects/ruby/spec/ruby/core/process/ppid_spec.rb:3:in `<top (required)>'
```

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/