Project

General

Profile

Bug #15297

Appveyor - test-all failures & build warnings - bison 3.1 vs 3.2 ?

Added by MSP-Greg (Greg L) 11 days ago. Updated 9 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.6.0dev (2018-11-10 trunk 65649) [x64-mingw32]
[ruby-core:89767]

Description

Appveyor just updated their images. I have rarely seen build/compile warnings with mingw/gcc & Ruby.

There are two test-all failures:

TestRubyOptions#test_yydebug
TestRubyOptions#test_dump_yydebug_with_rflag

The warnings seem associated with these. Attached file has detail from logs. The appveyor builds are listed at:
https://ci.appveyor.com/project/MSP-Greg/ruby-loco/history

FYI, installed OpenSSL package is now 1.1.1.

2018-11-10_65649.log (8.51 KB) 2018-11-10_65649.log MSP-Greg (Greg L), 11/10/2018 05:31 AM

Related issues

Related to Ruby trunk - Bug #15284: Unintentional warnings with node.hClosed

History

#1 Updated by MSP-Greg (Greg L) 11 days ago

  • File deleted (2018-11-10_65649.log)

#3 [ruby-core:89768] Updated by MSP-Greg (Greg L) 10 days ago

  • Subject changed from Appveyor mingw new image - test-all failures & build warnings to Appveyor - test-all failures & build warnings - bison 3.1 vs 3.2 ?

Finally took the time to look at this, and started with bison, as it's used by both the mswin/vc builds and the mingw build.

Locally, with bison 3.2 (version in the new Appveyor images), I had the same warnings, and stopped the build.

Switching to bison 3.1, the build completed without warnings, and test_rubyoptions.rb passed.

If it would be helpful, I can generate both parse.c & ripper.c with bison 3.1 & 3.2 and post the files...

#4 [ruby-core:89769] Updated by MSP-Greg (Greg L) 10 days ago

After reverting to bison 3.1, ruby-loco passed on

ruby 2.6.0dev (2018-11-11 trunk 65664) [x64-mingw32]

#5 Updated by nobu (Nobuyoshi Nakada) 9 days ago

  • Related to Bug #15284: Unintentional warnings with node.h added

#6 [ruby-core:89771] Updated by nobu (Nobuyoshi Nakada) 9 days ago

  • Status changed from Open to Closed

Seems fixed by r65667, too.
Thank you.

Also available in: Atom PDF