Open ivanvc opened 4 months ago
/label area/testing
@ivanvc: The label(s) /label area/testing
cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor
. Is this label configured under labels -> additional_labels
or labels -> restricted_labels
in plugin.yaml
?
Hey @ivanvc, I would like to take this issue!
/assign @henrybear327
Please take a look at #17400 and #17401 as a reference.
Hi @ivanvc @jmhbnz , I'd like to take this issue.
/assign @thedtripp
Thanks @ivanvc for raising this issue.
- Linters shellcheck (silently), markdown_marker, revive, and goword are skipped by the CI (exclamation marks were intentionally added for emphasis)
I think we should make sure the linters aren't skipped, and resolve them one by one in PRs.
Bug report criteria
What happened?
There are some issues regarding the state of the linters in the CI.
fmt
PASS
. But they are not checked on the CI.I don't know the value of markdown_marker. And the bom check is skipped locally, too, with a comment that it can't run with Go modules.
This issue can be split into:
What did you expect to happen?
The CI should fail as linter checks are failing.
How can we reproduce it (as minimally and precisely as possible)?
PASSES=fmt ./test
Anything else we need to know?
After fixing the linting issues from 3.5 (#17401 and #17400), I discovered that 3.4 had its own linter issues.
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
No response