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.

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

testenvSettings.sh should only run once #5297

Open
llxia opened this issue May 9, 2024 · 10 comments
Open

testenvSettings.sh should only run once #5297

llxia opened this issue May 9, 2024 · 10 comments

Comments

@llxia
Copy link
Contributor

llxia commented May 9, 2024

When USE_TESTENV_PROPERTIES=true and DYNAMIC_COMPILE=false, testenvSettings.sh gets triggered twice - once in compile.sh and once before make <test>. This does not cause any issues, but it is not necessary.

source ./scripts/testenv/testenvSettings.sh

String makeTestCmd = "$RESOLVED_MAKE;cd ./aqa-tests; . ./scripts/testenv/testenvSettings.sh;cd ./TKG; \$MAKE $testParam"

Console output:

00:01:13.427  + bash ./compile.sh
00:01:13.427  Set values based on ./testenv/testenv.properties:
00:01:13.427  =========
00:01:13.427  TKG_REPO=https://github.com/adoptium/TKG.git
00:01:13.427  TKG_BRANCH=master
...
00:02:11.016  + MAKE=make
00:02:11.016  + cd ./aqa-tests
00:02:11.016  + . ./scripts/testenv/testenvSettings.sh
00:02:11.016  ++ set +x
00:02:11.016  Set values based on ./testenv/testenv.properties:
00:02:11.016  =========
00:02:11.016  TKG_REPO=https://github.com/adoptium/TKG.git
00:02:11.016  TKG_BRANCH=master
...

We should add an if statement in

String makeTestCmd = "$RESOLVED_MAKE;cd ./aqa-tests; . ./scripts/testenv/testenvSettings.sh;cd ./TKG; \$MAKE $testParam"

run . ./scripts/testenv/testenvSettings.sh only if DYNAMIC_COMPILE == true

@Sangyoon21
Copy link
Contributor

I could work on it

@Sangyoon21
Copy link
Contributor

@Hana3706 She would push the pull request on this with me.

@Sangyoon21
Copy link
Contributor

@smlambert Sorry but could you reassign it to @Hana3706. She is working on it

@smlambert
Copy link
Contributor

In order to assign to a contributor, they have to add a comment to the issue. @Hana3706 - please comment on this issue, to have it assigned to you. Thanks!

@Hana3706
Copy link

I am so sorry for the confusion. I will work on this issue :)

@smlambert
Copy link
Contributor

No problem Hana3706, it reminded us that we should update our Contributing.md document to mention that one must make a comment if they want to be assigned to an issue. :)

@Hana3706
Copy link

I am just a bit confused about what further changes I should make to this issue. So I would be very thankful for a simple tip...
Thanks :)

@llxia
Copy link
Contributor Author

llxia commented May 27, 2024

@Hana3706 Please see the comment: #5341 (comment)

@Hana3706
Copy link

Hana3706 commented Jun 4, 2024

I have updated the if statement however my new commit shows under issue #5341 and is pending for review
(I apologize am super confused)

@llxia
Copy link
Contributor Author

llxia commented Jun 4, 2024

@Hana3706 #5297 is the issue and #5341 is the PR. It is correct for the code to show in #5341.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

4 participants