Douglas Simon

Thanks for the offer @neomatrix369 Refactoring mx.py into smaller modules has been a long time, low priority task and it would great to get some help with that.

One problem you will run into is that there's no clear indication of what parts of mx.py are used downstream and will break if those parts are moved elsewhere. In...

Unfortunately the Travis gate for `mx` is very incomplete and so we mainly rely on testing mx on a number of downstream repos such as Graal internally. Testing your changes...

Sorry, the person who wrote `tests/mx.mxtests` is no longer with the team and I'm not sure if anyone else remaining understands it (maybe @gilles-duboscq ?).

The target version is currently both Python 2.7 and 3.6 and we gate on both. This was done to enable the transition to Python3 with the pending EOL of Python...

I spoke with @gilles-duboscq offline and we both agree you should just ignore `tests/mx.mxtests`. It doesn't even appear to contain any tests, but just infrastructure to write python based tests....

Eventually mx will support this architecture. Currently, no one on the GraalVM team (that I'm aware of) has such a machine. Maybe you want to submit a PR? If you...

So this just does a shallow clone? That would cause problems for mx operations on imported suites that need a full history. I don't know off the top of my...

Ok, sounds reasonable.

Have you seen a failure? If so, under what conditions? This should not fail as this code is only called when building the JVMCI JDK and when JVMCI is a...