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

[all][chore] Run govulncheck scan separately #20342

Merged
merged 8 commits into from
Apr 11, 2023

Conversation

lootek
Copy link
Contributor

@lootek lootek commented Mar 27, 2023

Description:

Make govulncheck scan run a separate one due to some occasional failures (lint run was being killed sometimes)

Link to tracking Issue:
The original issue: #19154 and the previous PR: #19400 which made govulncheck one of the items of the lint run.
Issue describing the issue I'm addressing in this PR: #20274

Testing:
n/a

Documentation:
n/a

@runforesight
Copy link

runforesight bot commented Mar 27, 2023

Foresight Summary

    
Major Impacts

build-and-test-windows duration(4 seconds) has decreased 30 minutes 16 seconds compared to main branch avg(30 minutes 20 seconds).
View More Details

✅  govulncheck workflow has finished in 3 minutes 13 seconds and finished at 27th Mar, 2023.


Job Failed Steps Tests
govulncheck -     🔗  N/A See Details

⭕  changelog workflow has finished in 4 seconds (2 minutes 11 seconds less than main branch avg.) and finished at 11th Apr, 2023.


Job Failed Steps Tests
changelog -     🔗  N/A See Details

⭕  build-and-test-windows workflow has finished in 4 seconds (30 minutes 16 seconds less than main branch avg.) and finished at 11th Apr, 2023.


Job Failed Steps Tests
windows-unittest-matrix -     🔗  N/A See Details
windows-unittest -     🔗  N/A See Details

✅  check-links workflow has finished in 48 seconds and finished at 11th Apr, 2023.


Job Failed Steps Tests
changed files -     🔗  N/A See Details
check-links -     🔗  N/A See Details

✅  telemetrygen workflow has finished in 1 minute 23 seconds and finished at 11th Apr, 2023.


Job Failed Steps Tests
build-dev -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details
publish-latest -     🔗  N/A See Details

✅  load-tests workflow has finished in 6 minutes 30 seconds (3 minutes 53 seconds less than main branch avg.) and finished at 11th Apr, 2023.


Job Failed Steps Tests
setup-environment -     🔗  N/A See Details
loadtest (TestIdleMode) -     🔗  N/A See Details
loadtest (TestBallastMemory|TestLog10kDPS) -     🔗  N/A See Details
loadtest (TestMetric10kDPS|TestMetricsFromFile) -     🔗  N/A See Details
loadtest (TestMetricResourceProcessor|TestTrace10kSPS) -     🔗  N/A See Details
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs) -     🔗  N/A See Details
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs) -     🔗  N/A See Details
loadtest (TestTraceAttributesProcessor) -     🔗  N/A See Details

✅  prometheus-compliance-tests workflow has finished in 9 minutes 52 seconds (⚠️ 3 minutes 30 seconds more than main branch avg.) and finished at 11th Apr, 2023.


Job Failed Steps Tests
prometheus-compliance-tests -     🔗  N/A See Details

✅  e2e-tests workflow has finished in 14 minutes 17 seconds and finished at 11th Apr, 2023.


Job Failed Steps Tests
kubernetes-test (v1.26.0) -     🔗  N/A See Details
kubernetes-test (v1.25.3) -     🔗  N/A See Details
kubernetes-test (v1.24.7) -     🔗  N/A See Details
kubernetes-test (v1.23.13) -     🔗  N/A See Details

✅  build-and-test workflow has finished in 35 minutes 39 seconds (11 minutes 2 seconds less than main branch avg.) and finished at 11th Apr, 2023.


Job Failed Steps Tests
setup-environment -     🔗  N/A See Details
govulncheck -     🔗  N/A See Details
checks -     🔗  N/A See Details
check-collector-module-version -     🔗  N/A See Details
check-codeowners -     🔗  N/A See Details
lint-matrix (receiver-0) -     🔗  N/A See Details
lint-matrix (receiver-1) -     🔗  N/A See Details
lint-matrix (processor) -     🔗  N/A See Details
lint-matrix (exporter) -     🔗  N/A See Details
lint-matrix (extension) -     🔗  N/A See Details
lint-matrix (connector) -     🔗  N/A See Details
lint-matrix (internal) -     🔗  N/A See Details
lint-matrix (other) -     🔗  N/A See Details
build-examples -     🔗  N/A See Details
correctness-metrics -     🔗  N/A See Details
correctness-traces -     🔗  N/A See Details
integration-tests -     🔗  N/A See Details
unittest-matrix (1.20, receiver-1) -     🔗  N/A See Details
unittest-matrix (1.20, exporter) -     🔗  N/A See Details
unittest-matrix (1.20, extension) -     🔗  N/A See Details
unittest-matrix (1.20, processor) -     🔗  N/A See Details
unittest-matrix (1.20, receiver-0) -     🔗  N/A See Details
unittest-matrix (1.20, connector) -     🔗  N/A See Details
unittest-matrix (1.20, internal) -     🔗  N/A See Details
unittest-matrix (1.20, other) -     🔗  N/A See Details
unittest-matrix (1.19, receiver-0) -     🔗  N/A See Details
unittest-matrix (1.19, receiver-1) -     🔗  N/A See Details
unittest-matrix (1.19, processor) -     🔗  N/A See Details
unittest-matrix (1.19, exporter) -     🔗  N/A See Details
unittest-matrix (1.19, extension) -     🔗  N/A See Details
unittest-matrix (1.19, connector) -     🔗  N/A See Details
unittest-matrix (1.19, internal) -     🔗  N/A See Details
unittest-matrix (1.19, other) -     🔗  N/A See Details
lint -     🔗  N/A See Details
unittest (1.20) -     🔗  N/A See Details
unittest (1.19) -     🔗  N/A See Details
cross-compile (darwin, amd64) -     🔗  N/A See Details
cross-compile (darwin, arm64) -     🔗  N/A See Details
cross-compile (linux, 386) -     🔗  N/A See Details
cross-compile (linux, amd64) -     🔗  N/A See Details
cross-compile (linux, arm) -     🔗  N/A See Details
cross-compile (linux, arm64) -     🔗  N/A See Details
cross-compile (linux, ppc64le) -     🔗  N/A See Details
cross-compile (windows, 386) -     🔗  N/A See Details
cross-compile (windows, amd64) -     🔗  N/A See Details
build-package (rpm) -     🔗  N/A See Details
build-package (deb) -     🔗  N/A See Details
windows-msi -     🔗  N/A See Details
publish-check -     🔗  N/A See Details
publish-dev -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details
rotate-milestone -     🔗  N/A See Details

🔎 See details on Foresight

*You can configure Foresight comments in your organization settings page.

@lootek
Copy link
Contributor Author

lootek commented Mar 27, 2023

Right now there are govulncheck scans added at 3 different levels (in order of my personal preference):

  1. as a job in build-and-test workflow: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4532929300/jobs/7985062069 (clearly visually separated from the rest of stuff being done in there, yet still a part of building-and-testing routine)
  2. as a workflow: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4532929327 (too separate for me, imo it does not deserve that special treatment ;) )
  3. as a step in checks job in build-and-test workflow: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4532929300/jobs/7985099551 (imo hidden too deeply but now when I have some better understanding of the GH actions here I think it fits here perfectly regarding the semantics)

If the reviewer(s) agree, I'd stick to the 1st option but I'm open to discussing the other ones as well :)

The 4th possible option is how it was done previously in #19400 - as one of the linters (dependent Makefile target) called in lint step in build-and-test workflow - hidden even deeper, plus it suffered from being occasionally killed by the runner.

@lootek
Copy link
Contributor Author

lootek commented Mar 27, 2023

[proposed label] Skip Changelog

@lootek lootek marked this pull request as ready for review March 27, 2023 14:37
@lootek lootek requested review from a team and dashpole March 27, 2023 14:37
@dmitryax
Copy link
Member

[proposed label] Skip Changelog

[chore] tag in the PR title has the same effect :)

@dmitryax dmitryax added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Mar 28, 2023
@lootek lootek changed the title [all] Run govulncheck scan separately [all][chore] Run govulncheck scan separately Mar 29, 2023
@lootek lootek requested review from dmitryax and removed request for dashpole March 29, 2023 05:02
.github/workflows/build-and-test.yml Outdated Show resolved Hide resolved
.github/workflows/build-and-test.yml Outdated Show resolved Hide resolved
@lootek lootek requested a review from dmitryax March 29, 2023 08:54
Copy link
Member

@dmitryax dmitryax left a comment

Choose a reason for hiding this comment

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

LGTM

@dmitryax dmitryax self-requested a review April 6, 2023 15:49
.github/workflows/build-and-test.yml Outdated Show resolved Hide resolved
@lootek lootek requested a review from dmitryax April 11, 2023 15:19
Copy link
Member

@dmitryax dmitryax left a comment

Choose a reason for hiding this comment

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

Thank you @lootek. Can you please update go version in https://github.com/open-telemetry/opentelemetry-collector-releases? That repository the one producing the actual builds

@dmitryax dmitryax merged commit fa04914 into open-telemetry:main Apr 11, 2023
@github-actions github-actions bot added this to the next release milestone Apr 11, 2023
@lootek
Copy link
Contributor Author

lootek commented Apr 12, 2023

Can/should I also add that govulncheck run to the https://github.com/open-telemetry/opentelemetry-collector repo?

@dmitryax
Copy link
Member

Can/should I also add that govulncheck run to the https://github.com/open-telemetry/opentelemetry-collector repo?

Yes, please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants