Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@wgahnagl
Copy link
Contributor

@wgahnagl wgahnagl commented Oct 12, 2020

What type of PR is this?

/kind api-change
/kind bug

/kind cleanup

/kind dependency-change
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

simplifies the pod.bats file by removing excessive use of run

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

@openshift-ci-robot openshift-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. dco-signoff: no Indicates the PR's author has not DCO signed all their commits. labels Oct 12, 2020
@openshift-ci-robot
Copy link

Hi @wgahnagl. Thanks for your PR.

I'm waiting for a cri-o 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.

@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 Oct 12, 2020
@openshift-ci-robot openshift-ci-robot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. and removed dco-signoff: no Indicates the PR's author has not DCO signed all their commits. labels Oct 12, 2020
@haircommander
Copy link
Member

/ok-to-test

@openshift-ci-robot openshift-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 12, 2020
@codecov
Copy link

codecov bot commented Oct 12, 2020

Codecov Report

Merging #4257 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4257   +/-   ##
=======================================
  Coverage   38.57%   38.57%           
=======================================
  Files         111      111           
  Lines        8897     8897           
=======================================
  Hits         3432     3432           
  Misses       5081     5081           
  Partials      384      384           

@openshift-ci-robot openshift-ci-robot added dco-signoff: no Indicates the PR's author has not DCO signed all their commits. and removed dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Oct 12, 2020
@openshift-ci-robot openshift-ci-robot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. and removed dco-signoff: no Indicates the PR's author has not DCO signed all their commits. labels Oct 12, 2020
@kolyshkin
Copy link
Collaborator

  1. couple of whitespace nits.
  2. in some cases there's an extra cleanup which should not be there.

For example, @test "pod release name on remove" should look like this (schematically):

runp
stopp
rmp
runp

i.e. the second cleanup should not be part of the test as we're checking the pod with the same name can be recreated, and not checking that the second pod can be removed.

@kolyshkin
Copy link
Collaborator

  1. Looks like "pod list filtering" test has unneeded cleanup as well.

  2. As it comes for commit messages, it would be nice to have subjects like

test/pod.bats: ...

so a reader would see where the changes are made right away. As someone who reads git history a lot, I can attest that if the message starts with a file name, directory, subsystem name, package name, top-level feature or something like this, it makes it easier to visually filter what you're looking for.

Of course this is super minor. I wish I can point out to some kind of "best practices" doc for git commits but I don't have any :(

@wgahnagl wgahnagl force-pushed the refactor_tests branch 4 times, most recently from 0f1beff to f853472 Compare October 14, 2020 15:16
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 14, 2020
test/pod.bats Outdated
run systemctl list-units --type=slice
echo "$output"
[ "$status" -eq 0 ]
crictl runp "$TESTDIR"/sandbox_systemd_cgroup_parent.json
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: whitespace

test/pod.bats Outdated
Comment on lines 196 to 197
echo "$output" | grep 'TimeoutStopUSec=' || true # show
echo "$output" | grep -q '^TimeoutStopUSec=1min 28s$' # check
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm, can't understand why these two lines have changed

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 14, 2020

@wgahnagl: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws f853472 link /test e2e-aws
ci/openshift-jenkins/e2e_fedora a7b5ef7 link /test e2e_fedora
ci/openshift-jenkins/e2e_crun a7b5ef7 link /test e2e_crun
ci/openshift-jenkins/e2e_crun_cgroupv2 a7b5ef7 link /test e2e_cgroupv2
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. I understand the commands that are listed here.

Copy link
Collaborator

@kolyshkin kolyshkin left a comment

Choose a reason for hiding this comment

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

LGTM

@kolyshkin
Copy link
Collaborator

/retest

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kolyshkin, mrunalp, wgahnagl

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 Oct 14, 2020
@mrunalp
Copy link
Member

mrunalp commented Oct 14, 2020

@wgahnagl could you edit and add release note?

@openshift-ci-robot openshift-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 14, 2020
@mrunalp
Copy link
Member

mrunalp commented Oct 14, 2020

/retest

@mrunalp
Copy link
Member

mrunalp commented Oct 14, 2020

/lgtm (from kir's review)

@mrunalp
Copy link
Member

mrunalp commented Oct 14, 2020

/lgtm

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

/retest

@openshift-merge-robot openshift-merge-robot merged commit e7c64e8 into cri-o:master Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants