Closed ArangoGutierrez closed 3 months ago
/cc @BenTheElder @marquiz
/test pull-test-infra-verify-lint
failing linters
/approve /hold
/test pull-test-infra-verify-lint
failing linters
the lints that trigger the failure are not on NFD files, how can we pass by this, should I rebase on master or something?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ArangoGutierrez, BenTheElder
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test pull-test-infra-unit-test
/hold cancel /retest
config/jobs/kubernetes-sigs/node-feature-discovery/node-feature-discovery-postsubmits.yaml
31:24 error trailing spaces (trailing-spaces)
77:26 error no new line character at the end of file (new-line-at-end-of-file)
77:24 error trailing spaces (trailing-spaces)
the lints that trigger the failure are not on NFD files, how can we pass by this, should I rebase on master or something?
the other lints are warnings, which are not the failure, NFD is failing (see above, you can click to expand the log lines for more detail)
the lints that trigger the failure are not on NFD files, how can we pass by this, should I rebase on master or something?
the other lints are warnings, which are not the failure, NFD is failing (see above, you can click to expand the log lines for more detail)
Fixed
@ArangoGutierrez: Updated the job-config
configmap in namespace default
at cluster test-infra-trusted
using the following files:
node-feature-discovery-postsubmits.yaml
using file config/jobs/kubernetes-sigs/node-feature-discovery/node-feature-discovery-postsubmits.yaml
node-feature-discovery-presubmits-master.yaml
using file config/jobs/kubernetes-sigs/node-feature-discovery/node-feature-discovery-presubmits-master.yaml
node-feature-discovery-presubmits-release-0-16.yaml
using file config/jobs/kubernetes-sigs/node-feature-discovery/node-feature-discovery-presubmits-release-0-16.yaml
As seen at https://groups.google.com/a/kubernetes.io/g/dev/c/p6PAML90ZOU