-
-
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
testenvSettings.sh should only run once #5297
Comments
I could work on it |
@Hana3706 She would push the pull request on this with me. |
@smlambert Sorry but could you reassign it to @Hana3706. She is working on it |
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! |
I am so sorry for the confusion. I will work on this issue :) |
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. :) |
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... |
@Hana3706 Please see the comment: #5341 (comment) |
I have updated the if statement however my new commit shows under issue #5341 and is pending for review |
Signed-off-by: Hana Mostafa <[email protected]>
When USE_TESTENV_PROPERTIES=true and DYNAMIC_COMPILE=false, testenvSettings.sh gets triggered twice - once in
compile.sh
and once beforemake <test>
. This does not cause any issues, but it is not necessary.aqa-tests/compile.sh
Line 12 in 83bec27
aqa-tests/buildenv/jenkins/JenkinsfileBase
Line 9 in 83bec27
Console output:
We should add an if statement in
aqa-tests/buildenv/jenkins/JenkinsfileBase
Line 9 in 83bec27
run
. ./scripts/testenv/testenvSettings.sh
only if DYNAMIC_COMPILE == trueThe text was updated successfully, but these errors were encountered: