VectorAPI testing infrastructure minor fixes

[Paul Sandoz]

Looks ok.

A reminder that its really easy to run these tests using jtreg [1], and you don’t need to worry about compilation or class path setup, just point jtreg at the JDK build .e.g.:

  jtreg -jdk:./build/macosx-x64/jdk/ -ea -esa -avm -va -nr test/jdk/jdk/incubator/vector/

Further, you can run in verbose mode (-va) and obtain a script to execute directly after compilation to debug, either the Java bits or the VM, on a failure.

Paul.

[1] http://openjdk.java.net/jtreg/

> On Mar 7, 2018, at 2:15 PM, Halimi, Jean-Philippe <jean-philippe.halimi at intel.com> wrote:
> 
> Dear all,
> 
> I have made a quick follow-up patch for the VectorAPI Testing infrastructure. It basically fixes a couple of minor bugs and also enables auto-OS detection in order to accommodate the scripts automatically. I also added a few notes in the README based on the feedback I received. Feel free to review and comment on the following patch:
> 
> http://cr.openjdk.java.net/~rlupusoru/panama/webrev_testinginfra_fixes_00/
> 
> Thanks,
> 
> Jp