From: "MSP-Greg (Greg L)" Date: 2021-12-02T02:23:07+00:00 Subject: [ruby-core:106377] [Ruby master Bug#18379] [CI] Windows mingw\ucrt - test-all timeout failures Issue #18379 has been reported by MSP-Greg (Greg L). ---------------------------------------- Bug #18379: [CI] Windows mingw\ucrt - test-all timeout failures https://bugs.ruby-lang.org/issues/18379 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * ruby -v: ruby 3.1.0dev (2021-12-02T00:21:50Z master fe1725236c) [x64-mingw32] * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- Recently there was another test-all timeout failure on a Windows mingw or ucrt job. These are intermittent failures, and the last indicated that the test suite had passed. See https://github.com/ruby/ruby/runs/4389116424?check_suite_focus=true#step:16:909 ruby-loco runs tests differently, but it has also had intermittent failures, which were due to a ruby process that wasn't closing, leaving a locked file (STDERR mapped to a file). I added `Stop-Process -Name ruby -Force -ErrorAction SilentlyContinue` (PowerShell), which in Ruby's CI could be added right after the test-all line. Again, this is intermittent. I haven't checked to see if it can be repro'd using the test seed value from a failing job. -- https://bugs.ruby-lang.org/ Unsubscribe: