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

[exporter/awsxray] Flaky test TestXrayAndW3CSpanTraceResourceExtraction #21094

Closed
atoulme opened this issue Apr 20, 2023 · 5 comments
Closed
Labels

Comments

@atoulme
Copy link
Contributor

atoulme commented Apr 20, 2023

Component(s)

exporter/awsxray

What happened?

Flaky test with https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4757846016/jobs/8455186394?pr=21089

make -C exporter/awsxrayexporter test
make[2]: Entering directory '/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/exporter/awsxrayexporter'
go test -race -timeout 300s -parallel 4 --tags="" ./...
--- FAIL: TestXrayAndW3CSpanTraceResourceExtraction (0.00s)
    awsxray_test.go:70: 
        	Error Trace:	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/exporter/awsxrayexporter/awsxray_test.go:70
        	Error:      	"[%!s(*string=0xc00030e3b0) %!s(*string=0xc00030e[50](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4757846016/jobs/8455186394?pr=21089#step:8:51)0) %!s(*string=0xc00030e890)]" should have 2 item(s), but has 3
        	Test:       	TestXrayAndW3CSpanTraceResourceExtraction
        	Messages:   	2 spans have xay trace id
FAIL
FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsxrayexporter	0.3[53](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4757846016/jobs/8455186394?pr=21089#step:8:54)s

Collector version

latest

Environment information

No response

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

@atoulme atoulme added bug Something isn't working flaky test a test is flaky labels Apr 20, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

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

@github-actions
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 Jun 20, 2023
@codeboten
Copy link
Contributor

@github-actions
Copy link
Contributor

github-actions bot commented Sep 6, 2023

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 6, 2023
Copy link
Contributor

github-actions bot commented Nov 5, 2023

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 5, 2023
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

2 participants