Skip to content
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

Check stderr when running agent #142

Closed
wants to merge 1 commit into from
Closed

Conversation

razo7
Copy link
Member

@razo7 razo7 commented Apr 10, 2024

Why we need this PR

Considering a successful command execution when the return value is zero, no error, and stderr is empty as well.

Changes made

  • Include a check for stderr being empty when considering a successful agent execution.

Which issue(s) this PR fixes

Fixes (somehow) ECOPROJECT-1938

Test plan

Considering a successful command execution when return value is zero, no error, and stderr is empy as well
Copy link
Contributor

openshift-ci bot commented Apr 10, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Apr 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: razo7

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@@ -127,7 +127,7 @@ func (e *Executer) runWithRetry(ctx context.Context, uid types.UID, command []st
ctxWithTimeout, cancel := context.WithTimeout(ctx, timeout)
defer cancel()
stdout, stderr, faErr = e.runner(ctxWithTimeout, command)
if faErr == nil {
if faErr == nil && stderr == "" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stderr stream isn't an indication for an actual error!
e.g. curl uses stderr for verbose info, and stdout for the actual result

/hold

Copy link
Contributor

openshift-ci bot commented Jun 29, 2024

@razo7: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/4.17-ci-bundle-my-bundle fb9cef9 link true /test 4.17-ci-bundle-my-bundle
ci/prow/4.17-images fb9cef9 link true /test 4.17-images

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@slintes
Copy link
Member

slintes commented Jul 1, 2024

/close

Copy link
Contributor

openshift-ci bot commented Jul 1, 2024

@slintes: Closed this PR.

In response to this:

/close

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-sigs/prow repository.

@openshift-ci openshift-ci bot closed this Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants