"""error: module testng reads package test from both test and testng"""

[Martin Buchholz]

On Tue, Aug 29, 2017 at 3:36 PM, Jonathan Gibbons <
jonathan.gibbons at oracle.com> wrote:

> Martin,
>
> Sorry to be late to the party.
>
> I understand you're running some standard jdk tests, such as
> jdk/test/java/lang/ModuleTests/addXXX/Driver.java.
> I see the test explicitly requests /othervm mode.
> Is there anything else special I should know about how you are trying to
> run the test?   Are you running concurrently with any other tests, or just
> this one test by itself.
>

I can repro the failure running the test by itself.  (but naturally the
failure was discovered running together with others)

Are there any unusual permissions on the JTwork/modules directory, or its
> contents?
>

We always recreate JTwork fresh each jtreg invocation.


> I know "you guys" use a lot of symbolic links.   Anything to be aware of
> there?
>

I'm doing my testing here on my personal Ubuntu machine, deliberately free
of googleisms.

And the testng.jar files are readable, and @run testng works.


> jtreg should be setting up the module path in the same way. If jtreg omits
> an entry from the module path, one cause can be that the item is not found
> (or unreadable). But given the path is set up OK for compilation, it seems
> strange that the same or similar code would not work shortly afterwards at
> runtime.
>
> The test works for me, on a newly-build JDK 10, with no pre-existing
> JTwork, JTreport, on a fairly ordinary Ubuntu 14.04 system as well.
>

Hmmmm.... a mystery.