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

Skip to content

Conversation

@kolyshkin
Copy link
Collaborator

What type of PR is this?

/kind bug

What this PR does / why we need it:

This fixes running go mod tidy as a part of make vendor target.
Please see commits for details.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

@openshift-ci-robot openshift-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/bug Categorizes issue or PR as related to a bug. labels Sep 17, 2020
@codecov
Copy link

codecov bot commented Sep 17, 2020

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4208   +/-   ##
=======================================
  Coverage   39.06%   39.06%           
=======================================
  Files         111      111           
  Lines        8731     8731           
=======================================
  Hits         3411     3411           
  Misses       4944     4944           
  Partials      376      376           

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

mrunalp commented Sep 17, 2020

@saschagrunert ptal

Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

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

LGTM

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

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

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:
  • OWNERS [mrunalp,saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@saschagrunert
Copy link
Member

/retest

@haircommander
Copy link
Member

wow good find, unfortunately, you've got a merge conflict

@TomSweeneyRedHat
Copy link
Contributor

LGTM
but a rebase is needed @kolyshkin

@kolyshkin
Copy link
Collaborator Author

rebased

@haircommander
Copy link
Member

/lgtm

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

Added more changes (removed GO111MODULE and -mod=vendor, slightly improved CONTRIBUTING.md)

@kolyshkin
Copy link
Collaborator Author

kolyshkin commented Sep 18, 2020

CI error in integration_rhel is unrelated. It comes from

[ "$status" -eq 0 ]

which is trying to remove pod (should probably not be the part of the test).

The error is:

removing the pod sandbox "0d30f7428dba595155095cbfa805bad939876f05529ff6438ade6c2848ea9b9c": rpc error: code = Unknown desc = unable to remove managed namespaces: Removing namespaces encountered the following errors [unlinkat /var/run/netns/4302c201-43fd-4cd1-9cc0-efbba1762f3d: device or resource busy]

The pod is then removed successfully from teardown().

@kolyshkin
Copy link
Collaborator Author

/retest

@kolyshkin
Copy link
Collaborator Author

integration-rhel failed again, also while removing a pod, same problem, different test case (same file though), different namespace though.

removing the pod sandbox "ab9323d6260790ac37c994417911f432ccd6ef3f00184379df23cbdc15ad4b55": rpc error: code = Unknown desc = unable to remove managed namespaces: Removing namespaces encountered the following errors [unlinkat /var/run/utsns/ff1968b2-a9f2-420e-9ed3-b97651d8999c: device or resource busy unlinkat /var/run/ipcns/ff1968b2-a9f2-420e-9ed3-b97651d8999c: device or resource busy]

Might be related to commit ab82e12 as it speeds things up (by removing unnecessary code) and now namespace removal happens a bit earlier.

Not sure though why I'm the only one seeing this (and it's def unrelated to what is done in this PR)

@kolyshkin
Copy link
Collaborator Author

/retest

@kolyshkin
Copy link
Collaborator Author

/retest

@mrunalp
Copy link
Member

mrunalp commented Sep 22, 2020

/lgtm

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

integration-rhel failed again, also while removing a pod, same problem, different test case (same file though), different namespace though.

FYI this is addressed by #4217

Commit 25eb7d8 added this target. Alas, the `go mod tidy` never
worked, as it was written as part of `export` statement:

	export GO111MODULE=on \
		$(GO) mod tidy && \
		...

which is the same as

	export GO111MODULE=on $(GO) mod tidy && ...

which exports a bunch of variables, such as `go`, `mod`, and `tidy`
(or would export them if they existed), but does not run `go mod tidy`.

The fix would be to add a semicolon after the `export` statement,
but it looks like GO111MODULE=on is not needed, so just remove it.

While at it, && are no longer needed either, so remove them as well.

For GOSUMDB, export it for the target via Makefile

Signed-off-by: Kir Kolyshkin <[email protected]>
While at it, fix punctuation and improve some formatting.

Signed-off-by: Kir Kolyshkin <[email protected]>
GO111MODULE=on is not required for quite some time.

go -mod=vendor is the default even when GOPATH is set since go 1.14.

Signed-off-by: Kir Kolyshkin <[email protected]>
I suspect it was required to use vendor subdir.
It is no longer required as of go 1.13 or so.

Signed-off-by: Kir Kolyshkin <[email protected]>
The previous commit fixes running `go mod tidy` as part of `make vendor`
target.

This commit is the result of running fixed `make vendor`.

Signed-off-by: Kir Kolyshkin <[email protected]>
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Sep 29, 2020
@kolyshkin
Copy link
Collaborator Author

rebased on top of just-merged #4217; let's see how CI goes

@kolyshkin
Copy link
Collaborator Author

A bunch of weird errors from ci/prow/e2e-aws logs here, for example:

nodes/ip-10-0-136-92.us-west-2.compute.internal/journal.gz:Sep 29 01:22:55.326053 ip-10-0-136-92 kernel: ovs-vswitchd[2490]: segfault at 21 ip 0000556a8c3d93d4 sp 00007ffc0fb172c0 error 4 in ovs-vswitchd[556a8c06d000+629000]

Otherwise everything seems much better.

/test e2e-aws

@openshift-ci-robot
Copy link

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

Test name Commit Details Rerun command
ci/prow/e2e-aws 1a35fce link /test e2e-aws

Full PR test history. Your PR dashboard.

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.

@haircommander
Copy link
Member

I'm not convinced e2e-aws ever really passes on master, I think there's something up with the setup.
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 29, 2020
@openshift-merge-robot openshift-merge-robot merged commit 65d61df into cri-o:master Sep 29, 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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. 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