From: Eric Wong <normalperson@...>
Date: 2018-07-06T01:22:15+00:00
Subject: [ruby-core:87827] Re: [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process

Greg.mpls@gmail.com wrote:
> Below is the out from `ruby --jit -e exit`
> 
> ```
> C:\Greg\GitHub> ruby --jit -e exit
> process.c: sigchld=0 getpid.size=8 rb_pid_t.size=8
> mjit.c: sigchld=0 getpid.size=8 pid_t.size=8
> mjit.c: _WIN32 __MINGW32__ __MINGW64__ !__CYGWIN__
> ```

```
Thanks.  Were there any compiler warnings building process.c or mjit.c?

> Hope that helps.  Both Appveyor build & local buidl have the same output.

So nothing showed up from test-all?  Did you try verbose (TESTS=-v) output?
Perhaps trying a quick individual tests (e.g. test_pp.rb).
Something like:

	# should be an easy pass, especially if other suites are passing
	make test-all TESTS='test/test_pp.rb -v'

	make test-all TESTS='-v' # entire suite

Or maybe even add "V=1" to the make command to show more info
about what is executing:

	make test-all TESTS=-v V=1

Not sure what version of make you run, but maybe even "-d" flag
can help:

	make -d test-all TESTS=-v V=1

But yeah, really strange that even test-spec passes for you.
```

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>