Strange difference finding what to build (AIX vs. other platforms) in tools/jpackage/junit tests

[Baesken, Matthias]

Hello, I was recently running into a  strange difference  how the build command is set up on AIX vs. Linux .
See for more details  :
https://bugs.openjdk.org/browse/JDK-8316897

this happens in  the   tools/jpackage/junit/jdk.jpackage/jdk/jpackage/internal/  tests , e.g.   tools/jpackage/junit/jdk.jpackage/jdk/jpackage/internal/CompareDottedVersionTest.java

AIX (fails) :   this seems to collect all classes (with wrong package info??)  class by class

#section:build
----------messages:(3/691)----------
command: build jdk.jpackage.jdk.jpackage.internal.AppImageFileTest jdk.jpackage.jdk.jpackage.internal.ApplicationLayoutTest jdk.jpackage.jdk.jpackage.internal.CompareDottedVersionTest jdk.jpackage.jdk.jpackage.internal.DeployParamsTest jdk.jpackage.jdk.jpackage.internal.DottedVersionTest jdk.jpackage.jdk.jpackage.internal.EnquoterTest jdk.jpackage.jdk.jpackage.internal.InvalidDottedVersionTest jdk.jpackage.jdk.jpackage.internal.OverridableResourceTest jdk.jpackage.jdk.jpackage.internal.PathGroupTest jdk.jpackage.jdk.jpackage.internal.PlatformVersionTest jdk.jpackage.jdk.jpackage.internal.ToolValidatorTest


Linux (works nicely) :   this just detects  jdk.jpackage/*

#section:build
----------messages:(5/177)----------
command: build jdk.jpackage/*


Unfortunately  the verbose:all   trace of jtreg  does not tell me much helpful  about how  the commend is set up . Maybe this should be improved .
From a first look into the jtreg code, this might come from the Build – or Junit  action code, e.g. :

https://github.com/openjdk/jtreg/blob/ef3865581bdfc55c6315a8538222fc3a91b2b872/src/share/classes/com/sun/javatest/regtest/exec/JUnitAction.java#L130

am I right ?

Best regards, Matthias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jtreg-dev/attachments/20230925/2ab04cbf/attachment-0001.htm>