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

Bug 1892472: Run linter, utests, and gofmt in container #428

Merged
merged 2 commits into from Feb 1, 2021

Conversation

abhat
Copy link
Contributor

@abhat abhat commented Jan 29, 2021

Cherry-pick changes from github.com/ovn-org/ovn-kubernetes#1935 and github.com/ovn-org/ovn-kubernetes#1976 for running lint, gofmt, and utest jobs in containers.

Signed-off-by: Aniket Bhat anbhat@redhat.com

JacobTanenbaum and others added 2 commits January 29, 2021 08:46
upgrading the linter hits the regression below
Regression in golangci-lint: golangci/golangci-lint#1502

pin the version of the linter and run the linter in docker to ensure a
single version is used by CI and locally by developers

Signed-off-by: Jacob Tanenbaum <jtanenba@redhat.com>
(cherry picked from commit 0a9ef9f)
Allows for running tests inside of a container using docker or podman.

Signed-off-by: Vishwanath Jayaraman <vjayaram@redhat.com>
Co-authored-by: Aniket Bhat <anbhat@redhat.com>
(cherry picked from commit a666cbc)
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 29, 2021
@abhat
Copy link
Contributor Author

abhat commented Jan 29, 2021

/assign @trozet @alexanderConstantinescu

@abhat
Copy link
Contributor Author

abhat commented Jan 29, 2021

/test e2e-metal-ipi-ovn-ipv6

@abhat abhat changed the title Run linter, utests, and gofmt in container Bug 1892472: Run linter, utests, and gofmt in container Jan 29, 2021
@abhat
Copy link
Contributor Author

abhat commented Jan 29, 2021

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jan 29, 2021
@openshift-ci-robot
Copy link
Contributor

@abhat: This pull request references Bugzilla bug 1892472, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.0) matches configured target release for branch (4.7.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1892472: Run linter, utests, and gofmt in container

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
Copy link
Contributor

@abhat: This pull request references Bugzilla bug 1892472, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.0) matches configured target release for branch (4.7.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

/bugzilla refresh

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.

@abhat
Copy link
Contributor Author

abhat commented Jan 29, 2021

/test e2e-metal-ipi-ovn-ipv6

1 similar comment
@abhat
Copy link
Contributor Author

abhat commented Jan 30, 2021

/test e2e-metal-ipi-ovn-ipv6

@abhat
Copy link
Contributor Author

abhat commented Jan 31, 2021

/test e2e-openstack-ovn

@alexanderConstantinescu
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2021
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhat, alexanderConstantinescu

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

@@ -9,6 +9,18 @@ PKGS ?=
GOPATH ?= $(shell go env GOPATH)
TEST_REPORT_DIR?=$(CURDIR)/_artifacts
export TEST_REPORT_DIR
GO_DOCKER_IMG = quay.io/giantswarm/golang:1.15.7
Copy link
Contributor

Choose a reason for hiding this comment

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

do we trust this?

Copy link
Contributor

Choose a reason for hiding this comment

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

The standard is to use golang:1.15-alpine, which I realize is DockerHub. We could make this overridable with a ?= and point to a CI-hosted image for automated runs.

Copy link
Contributor Author

@abhat abhat Feb 1, 2021

Choose a reason for hiding this comment

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

Yeah, we can make this a downstream specific change. I think anything that is not hosted in Dockerhub which is relatively "official" will work.

Do you feel ok with merging this for now since this is a cherry-pick of upstream and I will create a downstream only PR to update that image to CI-hosted one?

Copy link
Contributor

Choose a reason for hiding this comment

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

it was mostly curiosity, not a blocking question :)

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2021

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

Test name Commit Details Rerun command
ci/prow/e2e-openstack-ovn 9c48e19 link /test e2e-openstack-ovn

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

@abhat
Copy link
Contributor Author

abhat commented Feb 1, 2021

/test e2e-gcp-ovn

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 7254852 into openshift:master Feb 1, 2021
@openshift-ci-robot
Copy link
Contributor

@abhat: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 1892472 has not been moved to the MODIFIED state.

In response to this:

Bug 1892472: Run linter, utests, and gofmt in container

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.

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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants