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/dockerstats] Failing integration test #31002

Open
djaglowski opened this issue Feb 1, 2024 · 7 comments
Open

[receiver/dockerstats] Failing integration test #31002

djaglowski opened this issue Feb 1, 2024 · 7 comments
Labels
flaky test a test is flaky help wanted Extra attention is needed receiver/dockerstats

Comments

@djaglowski
Copy link
Member

Component(s)

receiver/dockerstats

Describe the issue you're reporting

2024/02/01 17:24:45 Failed to get image auth for docker.io. Setting empty credentials for the image: docker.io/library/nginx:1.17. Error is:credentials not found in native keychain

...

 integration_test.go:132: 
        	Error Trace:	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/receiver/dockerstatsreceiver/integration_test.go:132
        	Error:      	Condition satisfied
        	Test:       	TestMonitoringAddedAndRemovedContainerIntegration
        	Messages:   	received undesired metrics
FAIL
FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver	14.126s

Observed here and here

@djaglowski djaglowski added the needs triage New item requiring triage label Feb 1, 2024
Copy link
Contributor

github-actions bot commented Feb 1, 2024

Pinging code owners:

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 May 27, 2024
@TylerHelmuth
Copy link
Member

Seeing this one on release day - we've run a lot of CI today and seen this frequently.

Copy link
Contributor

github-actions bot commented Sep 2, 2024

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 Sep 2, 2024
Copy link
Contributor

github-actions bot commented Nov 1, 2024

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 Nov 1, 2024
@dmitryax dmitryax added the help wanted Extra attention is needed label Dec 3, 2024
@dmitryax dmitryax reopened this Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky test a test is flaky help wanted Extra attention is needed receiver/dockerstats
Projects
None yet
Development

No branches or pull requests

5 participants