-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
Revive external_custom target #5812
Comments
FYI @sophia-guo (so you are aware that there is a Grinder job to test these cases) |
The first thing I see is the parameter is not passed
|
Hi @smlambert ! Can you please assign the issue to me? I would like to try and resolve it. Hopefully within a reasonable time. |
okay, I am gonna use this as a log of my thoughts, feel free to ignore, unless tagged.. https://ci.adoptium.net/view/Test_grinder/job/Grinder_ext_custom/24/consoleFull
since the check_external_custom_test is tested in a condition to be 1 or 0... |
andrlos@e5ef72a so the check_external_custom vs check_external_custom_test variable missmatch seems to be a part of the problem.. (grinder run)
|
52af986 the variable name missmatch of EXTERNAL_REPO_BRANCH vs EXTERNAL_CUSTOM_BRANCH seems to have been another problem and now we are on a correct version of the testsuite...
|
We had created a prototype under the Outreachy project called Tweetest, to be able to more easily extend external tests that meet a certain criteria (those that pull test material from a single repo, and use maven to run their tests).
Related: #2076
3 parameters were added to be able to trial out this idea (EXTERNAL_CUSTOM_REPO, EXTERNAL_CUSTOM_BRANCH and EXTERNAL_TEST_CMD which defaults to 'mvn clean install').
This issue is to revive the prototype and verify it works for some sample repositories. A Grinder job called Grinder_ext_custom has been created with the additional parameters. A recent run (Grinder_ext_custom/21) with the following parameter settings fails in the following way:
EXTERNAL_CUSTOM_REPO=https://github.com/radsz/jacop.git
EXTERNAL_CUSTOM_BRANCH=4.10.0
EXTERNAL_TEST_CMD=mvn --batch-mode clean install
Investigate the failure, and what recent changes to this area of code may have done to affect this target. Suspect we should be copying from external_custom/test.sh to /test.sh to be able to proceed.
The text was updated successfully, but these errors were encountered: