Skip to content

Conversation

saschagrunert
Copy link
Member

It looks like we're hitting the same issue as described in:
golangci/golangci-lint#827

As a workaround, we now disable the unused linter for now.

It looks like we're hitting the same issue as described in:
golangci/golangci-lint#827

As a workaround, we now disable the unused linter for now.

Signed-off-by: Sascha Grunert <[email protected]>
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 28, 2020
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Jan 28, 2020
@k8s-ci-robot k8s-ci-robot requested review from cpanato and dougm January 28, 2020 12:01
Copy link
Member

@cpanato cpanato left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 28, 2020
@hoegaarden
Copy link
Contributor

The issue talks about the error:

WARN [runner] Can't run linter goanalysis_metalinter: fact_purity: failed prerequisites: [email protected]/cozy/cozy-stack/model/instance/lifecycle [github.com/cozy/cozy-stack/model/app.test]

@saschagrunert How did you map that to the unused linter? Considering we get different errors for different PRs, I am not sure if there isn't a bigger problem somewhere and we are just trying random things? Or aren't those issues not related? I have no idea about golangci-lint. Recently it just annoys me most of the time! ;)

Anyhow, happy to merge if you think that's the appropriate fix.


#1040
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/release/1040/pull-release-test/1221841425608478720

level=warning msg="[runner] Can't run linter goanalysis_metalinter: fact_purity: failed prerequisites: [email protected]/release/pkg/notes/notesfakes [k8s.io/release/pkg/notes.test]"
level=error msg="Running error: fact_purity: failed prerequisites: [email protected]/release/pkg/notes/notesfakes [k8s.io/release/pkg/notes.test]"

#1044
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/release/1044/pull-release-test/1222146917287333888

level=warning msg="[runner] Can't run linter goanalysis_metalinter: ctrlflow: failed prerequisites: [email protected]/release/pkg/notes/notesfakes [k8s.io/release/pkg/notes.test]"
level=error msg="Running error: ctrlflow: failed prerequisites: [email protected]/release/pkg/notes/notesfakes [k8s.io/release/pkg/notes.test]"

#1043
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/release/1043/pull-release-test/1222120743693717504

level=warning msg="[runner] Can't run linter goanalysis_metalinter: ctrlflow: failed prerequisites: [email protected]/release/pkg/notes/notesfakes [k8s.io/release/pkg/notes.test]"
level=error msg="Running error: ctrlflow: failed prerequisites: [email protected]/release/pkg/notes/notesfakes [k8s.io/release/pkg/notes.test]"

Copy link
Contributor

@hasheddan hasheddan left a comment

Choose a reason for hiding this comment

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

It looks like a potential fix may be in place soon: golangci/golangci-lint#944

@saschagrunert
Copy link
Member Author

I basically tested it within the container image and now the issue seems gone. I did not dive into the issue that deep but I think since there are already fixes incoming we could live with that workaround here 🤷‍♂️ WDYT?

@justaugustus
Copy link
Member

justaugustus commented Jan 29, 2020

Let's keep an eye on those issues/PRs and pull in the fix when it's ready.
/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, justaugustus, saschagrunert

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 29, 2020
@k8s-ci-robot k8s-ci-robot merged commit 5fa50a9 into kubernetes:master Jan 29, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 29, 2020
@ernado
Copy link

ernado commented Feb 5, 2020

Referenced issue should be fixed in latest golangci-lint version, please CC me directly if it will break again.

@hasheddan
Copy link
Contributor

@ernado awesome! Thanks for following up here

@saschagrunert saschagrunert deleted the fix-golangci-lint branch February 5, 2020 20:17
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. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants