Hi,
The issue seems to be caused by changes in testng - but maybe that
needs to be fixed in the JAXP test base.
I could reproduce the issue by running the jaxp tests, after
unsetting JT_HOME and running with
https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/jtreg-4.2-b03.tar.gz
which has testng 6.9.11.
When I dowloaded
http://mvnrepository.com/artifact/org.testng/testng/6.9.5
and installed it in the jtreg install dir, the issue disappeared.
best regards,
-- daniel
On 22/11/16 13:31, Daniel Fuchs wrote:
Can it be that we are using a testng framework that is "too new" and
maybe contains something which makes it not work in the jaxp scenario?
When I call jtreg -version it reports:
TestNG: version 6.9.5
This seems different to what you are using.
Can you try with
https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/jtreg-4.2-b03.tar.gz
without altering the version of testng?
I had no problem running the tests with that version
of testng (except if I use the exploded build).
Maybe the listener that the test uses to set up the security
manager is invoked in a different way (earlier?) with the
6.9.10 version?
