Flaky Test - tailsamplingprocessor/TestConcurrentTraceArrival

[djaglowski]

race: limit on 8128 simultaneously alive goroutines is exceeded, dying
FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor	3.415s

Observed here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/6555994409?check_suite_focus=true

[djaglowski]

Here again: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/6578368988?check_suite_focus=true#step:8:2701

[djaglowski]

Here again: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/6595513232?check_suite_focus=true#step:7:2367

[djaglowski]

Another related failure: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/6928043103?check_suite_focus=true#step:7:2360

[djaglowski]

Related again: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/7113186690?check_suite_focus=true#step:7:2505

[dgoscn]

Hi @jpkrohling is this issue still open?

[jpkrohling]

I believe it is! Do you want to take this one?

[dgoscn]

Yes, can assign to me @jpkrohling

[djaglowski]

@dgoscn, assigned to you

[github-actions]

Pinging code owners: @jpkrohling. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

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:

• processor/tailsampling: @jpkrohling

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

[jpkrohling]

@dgoscn, are you still available to work on this one?

[dgoscn]

@jpkrohling I will have to let for someone else. If no one else assign, I want to go back to work on this as soon as possible

[dgoscn]

Hi @djaglowski How are you? Happy new year. Do you know if this scenario still happening? The log for the events are expired.
Thanks

[bryan-aguilar]

@dgoscn I was looking through the processor and was wondering if have you been able to replicate these flaky test locally? I ran the tests for a while on my machine and did not see any failures. Running it on an Intel MBP

[dgoscn]

Hey @bryan-aguilar. Thanks for the message, this sounds really good. I didn't made the tests again. But, sure I will do. Until the moment, I believe if you do not face the error, we can advance based on some advice from @jpkrohling .
Thanks

[ZenoCC-Peng]

Hello, I am currently review this test.

Upon running 20 times the GitHub Action on my personal branch, there were no test failures. Here is the file Tailsamplingprocessor-FlakyTest-#10205.xlsx
I suspect that someone may have modified the code.

If everything seems fine, I will proceed with pulling request.

[atoulme]

Please go ahead, thanks!

[jpkrohling]

Thanks!