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

Pipeline nightly release sometimes fails on linting timeout #211

Closed
afrittoli opened this issue Feb 4, 2020 · 3 comments
Closed

Pipeline nightly release sometimes fails on linting timeout #211

afrittoli opened this issue Feb 4, 2020 · 3 comments
Labels
area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/release Indicates an issue on release (process, tasks). kind/bug Categorizes issue or PR as related to a bug.

Comments

@afrittoli
Copy link
Member

Expected Behavior

The pipeline works

Actual Behavior

The linting task sometimes fails

Steps to Reproduce the Problem

Trigger a pipelinerun - or even directly the linting task:

k create job --from=cronjob/pipeline-cron-trigger-pipeline-nightly-release pipeline-cron-trigger-pipeline-nightly-release-timeout

Additional Info

level=info msg="[runner] Issues before processing: 311, after processing: 0"
level=info msg="[runner] Processors filtering stat (out/in): filename_unadjuster: 311/311, exclude-rules: 1/1, identifier_marker: 215/215, exclude: 1/215, nolint: 0/1, cgo: 311/311, path_prettifier: 311/311, skip_files: 311/311, skip_dirs: 215/311, autogenerated_exclude: 215/215"
level=info msg="[runner] processing took 163.75751ms with stages: skip_dirs: 41.343572ms, exclude: 35.927496ms, identifier_marker: 33.289256ms, path_prettifier: 28.207542ms, filename_unadjuster: 11.651277ms, autogenerated_exclude: 10.700937ms, nolint: 1.859581ms, cgo: 768.229µs, max_same_issues: 3.275µs, diff: 1.211µs, uniq_by_line: 1.107µs, max_from_linter: 842ns, source_code: 761ns, skip_files: 725ns, path_shortener: 715ns, exclude-rules: 659ns, max_per_file_from_linter: 325ns"
level=info msg="[runner] linters took 2m0.222550318s with stages: goanalysis_metalinter: 1m43.982837899s, unused: 16.075581672s"
level=info msg="File cache stats: 0 entries of total size 0B"
level=error msg="Timeout exceeded: try increase it by passing --timeout option"
level=info msg="Memory: 2498 samples, avg is 237.0MB, max is 2297.8MB"
level=info msg="Execution took 5m3.295881998s"
@afrittoli
Copy link
Member Author

/kind bug
/area dogfooding
/area release

@tekton-robot tekton-robot added kind/bug Categorizes issue or PR as related to a bug. area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/release Indicates an issue on release (process, tasks). labels Feb 4, 2020
@dibyom
Copy link
Member

dibyom commented Feb 5, 2020

The linting timeout has been hitting the triggers hard as well...seems especially bad for yaml/markdown lints 🤔

@bobcatfish
Copy link
Contributor

Whoops I made a duplicate - i think there's more info in #241 tho so im gonna close this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dogfooding Indicates an issue on dogfooding (aka using Pipeline to test Pipeline) area/release Indicates an issue on release (process, tasks). kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants