USHIFT-6175: Ginkgo releases tests are failing in CI#5518
USHIFT-6175: Ginkgo releases tests are failing in CI#5518openshift-merge-bot[bot] merged 20 commits intoopenshift:mainfrom
Conversation
|
@agullon: This pull request references USHIFT-6175 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@agullon: This pull request references USHIFT-6175 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
test/bin/scenario.sh
Outdated
| fi | ||
|
|
||
| # Run the tests and capture output with 10m timeout for every test case | ||
| if ! "${timeout_ginkgo}" run --timeout 10m --junit-dir="${test_results_dir}" -f "${case_selected}" 2>&1 | tee "${test_results_dir}/test-output.log"; then |
There was a problem hiding this comment.
Is not 10m too less ?
There was a problem hiding this comment.
for every test case, I think is more than enough. For example, on Jenkins, for release-4.20 branch 59 tests take less than 23 mins to run.
|
/retest |
1 similar comment
|
/retest |
|
/restest |
|
/retest |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/lgtm |
|
/retest-required |
|
/test e2e-aws-tests-arm |
|
/retest-required |
|
/retest |
|
/restes-required |
|
/restest-required |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
@agullon: This pull request references USHIFT-6175 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
/test e2e-aws-tests-bootc-release-arm |
…test-private repos are not in sync
|
/retest-required |
|
/test e2e-aws-tests-bootc-release |
|
@agullon: This pull request references USHIFT-6175 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@agullon: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agullon, kasturinarra 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 |
|
/verify by CI |
|
/verified by CI |
|
@agullon: This PR has been marked as verified by 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 openshift-eng/jira-lifecycle-plugin repository. |
USHIFT-6175: Ginkgo releases tests are failing in CI (cherry picked from commit 527f77d)
~Disruptivefiltermake allinstead ofmake buildcommand to update ginkgo repo to the latest versionopenshift-test-privaterepo to secure successful execution of test