Skip to content

Revert #6591 to fix issue with failed tests#6644

Merged
openshift-merge-robot merged 1 commit into
containers:masterfrom
jgallucci32:revert-log-follow
Jun 17, 2020
Merged

Revert #6591 to fix issue with failed tests#6644
openshift-merge-robot merged 1 commit into
containers:masterfrom
jgallucci32:revert-log-follow

Conversation

@jgallucci32
Copy link
Copy Markdown
Contributor

Signed-off-by: jgallucci32 john.gallucci.iv@gmail.com

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 17, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

Hi @jgallucci32. Thanks for your PR.

I'm waiting for a containers member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@TomSweeneyRedHat
Copy link
Copy Markdown
Member

/ok-to-test

@openshift-ci-robot openshift-ci-robot added ok-to-test and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 17, 2020
@TomSweeneyRedHat
Copy link
Copy Markdown
Member

LGTM
but I think @mheon had another thought elsewhere and I can't find it quickly.

Signed-off-by: jgallucci32 <john.gallucci.iv@gmail.com>
@jgallucci32
Copy link
Copy Markdown
Contributor Author

@TomSweeneyRedHat I did a rebase with the recent #6640 push from @edsantiago to verify his change in log testing still works and it has passed all the checks. This is ready for review.

@jgallucci32
Copy link
Copy Markdown
Contributor Author

/assign @umohnani8

@rhatdan
Copy link
Copy Markdown
Member

rhatdan commented Jun 17, 2020

@jgallucci32 This looks fine to me because it removes functionality, but does the logs --follow code work correctly after this reversal?

Does podman logs -f CTR work if Container is stopped? Paused?

If I am doing podman logs -F CTR and CTR is stopped, does podman logs stop?

LGTM

@jgallucci32
Copy link
Copy Markdown
Contributor Author

jgallucci32 commented Jun 17, 2020

@rhatdan No, this will reopen issue #6531 which is nessesary as the fix did more harm than good. Once reverted I plan to rebase PR #6614 to properly close the issue and make sure it doesn't reintroduce the check failures.

@TomSweeneyRedHat
Copy link
Copy Markdown
Member

This is all green now and I think will solve a number of CI tests issues once merged.

@rhatdan
Copy link
Copy Markdown
Member

rhatdan commented Jun 17, 2020

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgallucci32, rhatdan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 17, 2020
@rhatdan
Copy link
Copy Markdown
Member

rhatdan commented Jun 17, 2020

Ok Thanks @jgallucci32

@openshift-merge-robot openshift-merge-robot merged commit 5694104 into containers:master Jun 17, 2020
@jgallucci32 jgallucci32 deleted the revert-log-follow branch June 22, 2020 17:34
@github-actions github-actions Bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. ok-to-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants