From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.0 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id BD43F1F609 for ; Wed, 28 Nov 2018 18:41:31 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 6FC191216CA; Thu, 29 Nov 2018 03:41:29 +0900 (JST) Received: from o1678916x28.outbound-mail.sendgrid.net (o1678916x28.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 977F31216C7 for ; Thu, 29 Nov 2018 03:41:26 +0900 (JST) Received: by filter0103p3iad2.sendgrid.net with SMTP id filter0103p3iad2-12935-5BFEE152-10 2018-11-28 18:41:22.195171523 +0000 UTC m=+1118406.878329298 Received: from herokuapp.com (ec2-54-221-48-154.compute-1.amazonaws.com [54.221.48.154]) by ismtpd0045p1mdw1.sendgrid.net (SG) with ESMTP id ljelvsMASBqaNDXLO3X-1Q Wed, 28 Nov 2018 18:41:22.083 +0000 (UTC) Date: Wed, 28 Nov 2018 18:41:22 +0000 (UTC) From: Greg.mpls@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 65529 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15348 X-Redmine-Issue-Author: MSP-Greg X-Redmine-Sender: MSP-Greg X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS6cxNKx1RsghBRJzcBNzRH0P6z8rXS5292GeQ xmMqK2/i+avEvV4tEwgTpcSsN+YC/Vo1ZYW1J2mVFP07s7ov7dXyvMJmYFUvQyn2yw5CDTSmA9bxdi 9b7S4wXLmoK+d/TRUsepCn12A6EAKJB+ZgDtt9VNv1CHSVyPGcOpQovHRw== X-ML-Name: ruby-core X-Mail-Count: 90132 Subject: [ruby-core:90132] [Ruby trunk Bug#15348] r66003 Support targetting TracePoint - MinGW X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #15348 has been updated by MSP-Greg (Greg L). @ko1 Koichi, Thank you. Repeat that. ruby-loco is green. Going back to last year, I've have intermittent (and sometimes only on appveyor) issues with callcc, the (sometimes considerable) block nesting in the spec suite, and this issue, in which nesting, eval, and maybe using all came together. I finally created a repo so i could do 'custom tesing' without building just to see what was going on, as I mentioned, I couldn't repo this locally. Again, thanks, Greg ---------------------------------------- Bug #15348: r66003 Support targetting TracePoint - MinGW https://bugs.ruby-lang.org/issues/15348#change-75251 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- This has caused failures in spec/ruby/core/main/using_spec.rb, specifically the first spec. On Appveyor, trying several versions of both specs, the first one (`eval('using', TOPLEVEL_BINDING)`) fails, the second one (`eval('using "foo"', TOPLEVEL_BINDING)`) passes. Locally (Windows 10), all versions of both specs have always passed using the same build (saved as an artifact) from Appveyor... -- https://bugs.ruby-lang.org/