Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: update FAQ with correct AQA custom target parameter #3351

Merged
merged 1 commit into from
Mar 11, 2024
Merged

doc: update FAQ with correct AQA custom target parameter #3351

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,8 +208,10 @@ is more information on running tests yourself in the

A few examples that test specific pieces of infra-related functionality so useful to be aware of.
These are the parameters to pass into a Grinder job in jenkins. If using
these from the command line as per the example above, the `TARGET` name
should have an underscore `_` prepended to it.
these from the command line instead of a Grinder job there are a couple of
things regarding the information in this table:
- The `TARGET` name should have an underscore `_` prepended to it (like the shell snippet above)
- For custom targets, specify it as a JDK_CUSTOM_TARGET variable to make e.g. `make _jdk_custom JDK_CUSTOM_TARGET=java/lang/invoke/lambda/LambdaFileEncodingSerialization.java`

| `BUILD_LIST` | `TARGET` | `CUSTOM_TARGET` | What does it test? |
| --- | --- | --- | --- |
Expand Down
Loading