-
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
feat: support to produce results from a failed task #6510
feat: support to produce results from a failed task #6510
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
5ab2bb7
to
5270e26
Compare
/kind feature assigning to the reviewers of original pr: /assign @vdemeester |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
5270e26
to
afc4db7
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
looks like a flake, at least one of them didn't fail earlier:
Was able to run |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
/assign |
/retest |
So the alpha test failure is not a flake 😞 But it is interesting that the same test succeeds with The logs of tests with The logs of tests with The difference is: With
With
|
hey @chitrangpatel, do you think the configuration of |
@@ -208,7 +208,7 @@ func setTaskRunStatusBasedOnStepStatus(ctx context.Context, logger *zap.SugaredL | |||
} | |||
|
|||
taskResults, filteredResults := filterResults(results, specResults) | |||
if tr.IsSuccessful() { | |||
if tr.IsDone() { |
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 think you need to do the same thing in line 185 as well.
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.
That will account for the same change when fetching results from sidecar logs too.
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.
thanks a bunch @chitrangpatel for a quick response 🙏 hopefully works now 🤞
If the task fails or succeeds, as long as the task result is initialized, it can be successfully parsed and can be referenced by the final task. This commit enables the failed task to produce the task results, and the final task can reference it. Please see detailed description in issue tektoncd#5749 Co-authored-by: yang kewei <[email protected]> Signed-off-by: pritidesai <[email protected]> Signed-off-by: Priti Desai <[email protected]>
afc4db7
to
660e742
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
/retest |
/test pull-tekton-pipeline-go-coverage-df |
@pritidesai: The specified target(s) for
The following commands are available to trigger optional jobs:
Use 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. |
/retest |
Changes
If the task fails or succeeds, as long as the task result is initialized, it can be successfully parsed and can be referenced by the final task.
This commit enables the failed task to produce the task results, and the final task can reference it.
Closes #5749
This is a duplicate of #5750 but with conflicts resolved and e2e test. I was reviewing PR #5750 and decided to create an e2e test. After noticing it had merge conflicts, decided to resolve them and create this PR. @cugykw is now a co-author of this commit.
/kind feature
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