-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Label user error
for failure PipelineRun Status Message
#7475
Conversation
Skipping CI for Draft Pull Request. |
user error
for failure PipelineRun Status Reason
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
9919da1
to
fc6a2a1
Compare
One bit that is off is that when I label the error messages with "[User error]" label, it appears to me that I have to match the exact event strings while previously it only required to provide the first half of the strings. This does not make our tests more fragile though from my understanding. |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest |
user error
for failure PipelineRun Status Reasonuser error
for failure PipelineRun Status Message
Updated to label user message instead of reasons as we discussed how users would use reasons for downstream condition judgement. |
fc6a2a1
to
990189e
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
"Validation failed for pipelinerun with error %s", | ||
pipelineErrors.WrapUserError(err)) |
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.
do we need to include pipelinerun name here or it is added ?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Yongxuanzhang 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 |
990189e
to
4cddf6a
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
This commit labels the user errors for failed PipelineRun status. This aims to communicate explicitly with users of whether the run failed could be attributed to users' responsibility. /kind misc part of tektoncd#7276
This commit follows up tektoncd#7475 and labels user error for failed TaskRun status messages. It marks off user errors in the taskrun reconciler and communicate to users via TaskRunStatus condition messages. /kind misc part of tektoncd#7276
4cddf6a
to
ebbef9d
Compare
cc @tektoncd/core-maintainers |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Thanks 🎉 |
This commit follows up tektoncd#7475 and labels user error for failed TaskRun status messages. It marks off user errors in the taskrun reconciler and communicate to users via TaskRunStatus condition messages. /kind misc part of tektoncd#7276
This commit follows up tektoncd#7475 and labels user error for failed TaskRun status messages. It marks off user errors in the taskrun reconciler and communicate to users via TaskRunStatus condition messages. /kind misc part of tektoncd#7276
This commit follows up tektoncd#7475 and labels user error for failed TaskRun status messages. It marks off user errors in the taskrun reconciler and communicate to users via TaskRunStatus condition messages. /kind misc part of tektoncd#7276
This commit follows up tektoncd#7475 and labels user error for failed TaskRun status messages. It marks off user errors in the taskrun reconciler and communicate to users via TaskRunStatus condition messages. /kind misc part of tektoncd#7276
Changes
This commit labels the user errors for failed PipelineRun status. This aims to
communicate explicitly with users of whether the run failed could be
attributed to users' responsibility.
/kind misc
part of #7276
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes