Using an initial patch for supporting TestNG mixed mode support for JUnit, it is observed to work as expected in othervm mode, but not in agentvm mode.

From email:

I'm seeing different behavior when jtreg runs a new toy test in othervm mode, vs agentvm mode. It's reporting the number of test cases wrongly, and I believe it's a problem with the listener used to track the results.

I'm testing by comparing the results of two very simple, very similar tests -- except that one uses TestNG imports, the other uses JUnit imports. The tiny test suite is also attached.

When I run these two tests, and compare the .jtr files, there's a bunch of expected differences, of course, but this is part with the unacceptable differences. The first difference (test names) is OK, but note the rest of the differences; they're bad.

> ----------System.out:(14/288)----------
94c92
< testng/p/T1.java
---
> testng/p/T2.java
95a94
> test p.T2.test1(): success
96a96
> test p.T2.test2(): success
97a98
> test p.T2.test3(): success
100,101c101,102
< testng/p/T1.java
< Total tests run: 0, Failures: 0, Skips: 0
---
> testng/p/T2.java
> Total tests run: 3, Failures: 0, Skips: 0