[CI] Unit tests are failing due to timeout for setup-go

[kasia-kujawa]

Component(s)

No response

Describe the issue you're reporting

Unit tests are failing due to timeout for setup-go

For example:
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8707136104/job/23882045056
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8707700094/job/23883544181

[crobert-1]

Thanks for filing @kkujawa-sumo! I believe this is a duplicate of #32330

It looks like the latest two frequencies I've posted in the other bug are what you've shared here, but they're slightly different than the original failures there. I'll reopen this issue and move the latest frequencies on that bug to this one instead.

[crobert-1]

More frequencies:

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8668725178/job/23774313271?pr=32200
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8696281407/job/23849232881

[crobert-1]

+1 freq for Post Cache Go failure, I assume they're the same underlying cause: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8708439881/job/23885966005?pr=32443

[crobert-1]

+1 freq: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8708439881/job/23885948254?pr=32443

[crobert-1]

Potentially alleviated by #32450

[crobert-1]

+1 freq: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8743009049/job/23992771585?pr=31915

[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.

[github-actions]

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