-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[chore][cmd/otelcontribcol] Exclude from linter #27865
[chore][cmd/otelcontribcol] Exclude from linter #27865
Conversation
For some context and a relevant example of why this is necessary, I'm adding eks cluster name detection to the resource detection processor (#27408), and lint is failing every time either on timeouts or overloading the GitHub CI runner. |
Looks like that helped some. If you get in trouble again, adding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
**Description:** The linter runs are taking longer and longer as more components and dependencies are added, it's preferable to simply run on each individual component. **Link to tracking Issue:** Related: open-telemetry#27850
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Same idea as #27865, remove generated code from being linted. The linter is taking longer and longer to run as more components and dependencies are added. This change is to remove unnecessary modules from being linted, which will help reduce runtime and resources required. **Link to tracking Issue:** <Issue number if applicable> Related #27850
**Description:** The linter runs are taking longer and longer as more components and dependencies are added, it's preferable to simply run on each individual component. **Link to tracking Issue:** Related: open-telemetry#27850
…ry#27884) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Same idea as open-telemetry#27865, remove generated code from being linted. The linter is taking longer and longer to run as more components and dependencies are added. This change is to remove unnecessary modules from being linted, which will help reduce runtime and resources required. **Link to tracking Issue:** <Issue number if applicable> Related open-telemetry#27850
**Description:** The linter runs are taking longer and longer as more components and dependencies are added, it's preferable to simply run on each individual component. **Link to tracking Issue:** Related: open-telemetry#27850
…ry#27884) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Same idea as open-telemetry#27865, remove generated code from being linted. The linter is taking longer and longer to run as more components and dependencies are added. This change is to remove unnecessary modules from being linted, which will help reduce runtime and resources required. **Link to tracking Issue:** <Issue number if applicable> Related open-telemetry#27850
Description:
The linter runs are taking longer and longer as more components and dependencies are added, it's preferable to simply run on each individual component.
Link to tracking Issue:
Related: #27850