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
Bug 1873230: show message for retrying in conclusion if there are failed tasks #6465
Bug 1873230: show message for retrying in conclusion if there are failed tasks #6465
Conversation
@nemesis09: This pull request references Bugzilla bug 1873230, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
In 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. |
<SyncMarkdownView content={conclusion} /> | ||
{nextQuickStart && ( | ||
{tasks.map((task, index) => { | ||
if (allTaskStatuses[index] === QuickStartTaskStatus.FAILED) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need to check the status for each task like this. Just check if allTaskStatuses
has at least one failed
status in the array. If yes then show error message else show conclusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought i would avoid introducing a new loop and use the existing one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated the check to const hasFailedTask = allTaskStatuses.includes(QuickStartTaskStatus.FAILED);
5b42121
to
9e856d6
Compare
{nextQuickStart && ( | ||
<SyncMarkdownView | ||
content={ | ||
!hasFailedTask |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nemesis09 can you please reverse it. It's better to use positivity check, remove the !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
9e856d6
to
4eb1d14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested it locally, lgtm. All other good feedback is already addressed 👍
/lgtm |
ran it locally and it works fine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinandan13jan, jerolimov, nemesis09, rohitkrai03 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@nemesis09: All pull requests linked via external trackers have merged: Bugzilla bug 1873230 has been moved to the MODIFIED state. In 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. |
Fixes:
https://issues.redhat.com/browse/ODC-4638
Analysis / Root cause:
Currently when one or more steps have not been accomplished successfully, the Quick Start displays the positive conclusion message provided
Solution Description:
If one or more steps have not been accomplished successfully, on the last page of the Quick Start
Screens:
Before
After
Test Coverage:
Browser Conformance: