From: Greg.mpls@... Date: 2018-08-01T14:46:37+00:00 Subject: [ruby-core:88260] [Ruby trunk Bug#14957] MinGW, gcc 8.2.0, bootstraptest - failure ? Issue #14957 has been reported by MSP-Greg (Greg L). ---------------------------------------- Bug #14957: MinGW, gcc 8.2.0, bootstraptest - failure ? https://bugs.ruby-lang.org/issues/14957 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0dev (2018-08-01 trunk 64156) [x64-mingw32] ? * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- Very recently MSYS/MinGW updated gcc from 7.3.0 to 8.2.0. For the most part, every test suite runs fine except the bootstraptest test, which has a single failure on Appveyor: ``` #1379 test_thread.rb: Thread.new("foo", &Object.method(:class_eval)).join #=> killed by SIGSEGV (signal 11) [ruby-dev:34128] ``` I believe the test is here [bootstraptest/test_thread.rb:L334](https://github.com/ruby/ruby/blob/e62214be87a53045dbec187c66e208bc303e0f60/bootstraptest/test_thread.rb#L334-L336), code below: ``` assert_normal_exit %q{ Thread.new("foo", &Object.method(:class_eval)).join }, '[ruby-dev: 34128]' ``` This is the first time I recall seeing an error in btest, so I haven't really looked at the code. `assert_normal_exit` saves the string in a file, then runs it. When I use the string with `ruby -e`, I get: ``` # terminated with exception (report_on_exception is true): Traceback (most recent call last): -e:1:in `class_eval': Can't eval on top of Fiber or Thread (RuntimeError) ``` Not sure if that implies anything... Four of the builds using gcc 8.2.0 are on Appveyor, downloading and running locally, the following passes (from bootstraptest): ``` ruby -v runner.rb --ruby=C:/Greg/Ruby99-x64b/bin/ruby.exe -v --sets=thread ``` Let's say I'm confused, fails on Appveyor, passes locally, etc. If anyone has any suggestions... Thanks, Greg -- https://bugs.ruby-lang.org/ Unsubscribe: