Windows spec failure - Process.ppid returns the process id of the parent of this process - ??
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
../mspec/bin/mspec -rdevkit -j -T "--disable=gems" core
Updated by usa (Usaku NAKAMURA) over 2 years ago
- Status changed from Open to Closed
test-spec target of make,
RUBY_EXE constant in mspec is
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
Updated by MSP-Greg (Greg L) over 2 years ago
I revised appveyor.yml to run specs from the install folder, and submitted a PR. I think running at least one test suite from it is a good idea, as the purpose is to create an install.
So, I reverted the commit that bypassed the failing spec. Maybe Eregon (Benoit Daloze) can create a guard that considers both windows and whether