WIP. USHIFT-1387: add scenario test run script#1999
WIP. USHIFT-1387: add scenario test run script#1999pacevedom wants to merge 3 commits intoopenshift:mainfrom
Conversation
|
@pacevedom: This pull request references USHIFT-1387 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test microshift-metal-tests |
|
@pacevedom: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
I think we need to override the SCENARIO_INFO_DIR to point to the location in the artifact dir where the scenario data has been downloaded in the previous step. We might need a new variable in common.sh to make overriding all of the other directory variables easier.
There was a problem hiding this comment.
Yes, was just creating this commit to check whats needed from openshift/release and work it out from that starting point.
Base path for everything will also change once the microshift-test-payload image disappears, so we need to make it configurable in an easy way. Thanks for the heads up!
There was a problem hiding this comment.
Is the artifact dir shared between pods in the CI cluster? Or should we use the shared directory and then copy the content into the artifact directory separately?
There was a problem hiding this comment.
We can't do this in the scenario script because in CI several copies of this will eventually run in parallel. We could do it explicitly in the phase script instead.
c051d0d to
c113646
Compare
a8f0c72 to
ff61466
Compare
Which issue(s) this PR addresses:
Closes #