You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when running e.g. make test.JdiLoadTest I can't specify an individual test to run e.g. simple_launch. To do that I have to go right down to the perl layer underneath.
As I'm trying to investigate a failure in one test within the test suite adding this feature would make it easier to reproduce failures, as we could then allow the launching of single tests through jenkins directly. In effect I'm requesting the addition of TEST_ARGS="test=basic_launch" or something similar to the makefile.
The text was updated successfully, but these errors were encountered:
I'll add a test.Custom target in openjdk.build/makefile which one can then use as:
make test.Custom TEST=JdiTest TEST_ARGS="test=basic_launch" JAVA_ARGS="-Xint"
(TEST would be required, the other macros optional unless the TEST requires a -test-arg argument).
To enable execution on an AdoptOpenJDK test machine via Jenkins we will need a Jenkins job which allows a user to supply those macros via Parameters.
lumpfish
pushed a commit
to lumpfish/aqa-systemtest
that referenced
this issue
Sep 28, 2017
Currently when running e.g. make test.JdiLoadTest I can't specify an individual test to run e.g. simple_launch. To do that I have to go right down to the perl layer underneath.
As I'm trying to investigate a failure in one test within the test suite adding this feature would make it easier to reproduce failures, as we could then allow the launching of single tests through jenkins directly. In effect I'm requesting the addition of TEST_ARGS="test=basic_launch" or something similar to the makefile.
The text was updated successfully, but these errors were encountered: