Issue #14464 has been updated by MSP-Greg (Greg L).

File TestJIT_info_62380.txt added

@k0kubun,

Appveyor run of 62377 had the following (added backticks for web view):

```
Retrying...
[1/2]      8 TestJIT#test_compile_insns = 11.33 s = F
[2/2]      7 TestJIT#test_jit_output = 5.58 s = .

  1) Failure:
TestJIT#test_compile_insns [C:/projects/ruby-loco/src/ruby/test/ruby/test_jit.rb:30]:
Failed to run script with JIT:
'``
def foo(&b)
  a = b
  b = 2
  a.call + 2
end

print foo { 1 }

'``


stdout:
'``

'``


stderr:
'``
JIT success (1318.5ms): foo@-e:1 -> C:/Users/appveyor/AppData/Local/temp/_ruby_mjit_p12476u0.c
-e:2:in `foo': wrong argument type Binding (expected Class) (TypeError)
	from -e:7:in `<main>'
Successful MJIT finish

'``

.
<true> expected but was
<false>.
```

I ran the test locally, and I'm wondering what is using the /Users/user name/AppData/Local/temp folder, as on my system, all TEMP/TMP env variables are set to different folders.  I've built ruby for quite a while, and also MSYS2 packages, and I don't ever recall anything using that.  For many windows users, their user name may have a space (as mine does).  That hasn't been an issue with config files, --user-install gems, etc.

But, when I ran the tests, it mangles the path...

The test-all summary for TestJIT is attached for 62380.  I believe there are 9 failures & 5 skips in 64 tests?

Thanks again,

Greg


----------------------------------------
Bug #14464: MJIT & MinGW / gcc 7.3.0 seemed ok as of 62337, fail or skip after
https://bugs.ruby-lang.org/issues/14464#change-70299

* Author: MSP-Greg (Greg L)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.0dev (2018-02-11 trunk 62371) [x64-mingw32]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
First of all, a thank you to those working on MJIT.

At least three builds of ruby-loco MinGW passed the MJIT tests (62327, 62331, 62337), but after that, the tests have either failed or skipped.  First fail was at 62341.

The most recent build (2018-02-11 trunk 62371), skipped with no timeout error in `jit_supported?`  I haven't looked at patching `test_jit.rb` to see if I can get more info.

I don't know if this is a MinGW issue or a gcc 7.3.0 issue, but, given that it did work for a few builds, I would appreciate it if someone could look into it.  Anything I can help with, I'm happy to.

Thanks, Greg

---Files--------------------------------
TestJIT_info_62380.txt (33.4 KB)


-- 
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>