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

[receiver/carbon, exporter/carbon] Carbon LoadTests are failing #31275

Closed
TylerHelmuth opened this issue Feb 14, 2024 · 5 comments
Closed

[receiver/carbon, exporter/carbon] Carbon LoadTests are failing #31275

TylerHelmuth opened this issue Feb 14, 2024 · 5 comments
Labels

Comments

@TylerHelmuth TylerHelmuth added bug Something isn't working needs triage New item requiring triage priority:p2 Medium ci-cd CI, CD, testing, build issues flaky test a test is flaky and removed needs triage New item requiring triage labels Feb 14, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@TylerHelmuth
Copy link
Member Author

this is the first test were the panic started happening: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/7561357181/job/20590958008

PR: #30652

Copy link
Contributor

Pinging code owners for testbed: @open-telemetry/collector-approvers. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Apr 15, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant