-
-
Notifications
You must be signed in to change notification settings - Fork 314
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.
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
Non-container external tests broken #5403
Comments
Will work on fixing this issue. @sophia-guo Do you have a jenkins link so I can refer? Thanks. |
@LongyuZhang I don't have a public link. It could be reproduced by running any external tests other than CIRU. For example :lucene. |
|
Thanks for the info, created draft PR link to inherit |
Note that print_clone_project() update is not correct https://github.com/adoptium/aqa-tests/blob/master/external/dockerfile_functions.sh#L512. print_clone_project() is for git clone third party repo by github_url, not for aqa-tests specifically, which is defined in test.properties. Currently non-containers tests will get aqa-tests repo and third party branch.
|
ERROR: failed to solve: ENV must have two arguments
when make compile
Interesting auto closes doesn't work? Close it manually. |
external tests got
ERROR: failed to solve: ENV must have two arguments
whenmake compile
.Related with #5356
https://github.com/adoptium/aqa-tests/blob/master/external/dockerfile_functions.sh#L509
https://github.com/adoptium/aqa-tests/blob/master/external/dockerfile_functions.sh#L661
USE_TESTENV_PROPERTIES is not visible to print_testInfo_env() hence in generated Dockerfile USE_TESTENV_PROPERTIES no value. @LongyuZhang
Also Note:
With #5356 running locally will also hit the following message, which means both ADOPTOPENJDK_REPO and ADOPTOPENJDK_BRANCH need to be export. If that is the case, all README need to be updated. Wondered why we need to set ADOPTOPENJDK_REPO and ADOPTOPENJDK_BRANCH as environment variable instead of passing them in as all other parameters?
The text was updated successfully, but these errors were encountered: