Issue #15810 has been updated by MSP-Greg (Greg L). @usa 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 can create a guard that considers both windows and whether `RUNRUBY` exists... ---------------------------------------- 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-77829 * 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/ Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>