[exporter/datasetexporter]: Fix failing test on windows

[martin-majlis-s1]

Description: In the PR #21815 I have added code for dataset exporter. However test for windows - https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5002859274/jobs/8963342956 - is failing. So let's fix it.

Link to tracking Issue: #22039, #20660

Testing:

The issue is caused by the github.com/stretchr/testify/suite package. Once I have removed it started to work.

[martin-majlis-s1]

Library httptest is recommended and it's used everywhere. As well as problematic function - httptest.NewServer - https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-collector-contrib%20httptest.NewServer&type=code

[martin-majlis-s1]

@mx-psi : This is the PR, where I am trying to figure out, why is it failing.

[mx-psi]

@martin-majlis-s1 I added the 'Run Windows' label. Future commits to the PR's branch will run the test suite on Windows.

[martin-majlis-s1]

Message - " socket: The requested service provider could not be loaded or initialized." - is universal message in windows.

This is happening when the application does not have permissions - https://travis-ci.community/t/socket-the-requested-service-provider-could-not-be-loaded-or-initialized/1127 - but it's really strange, since it is used by everybody - #22041 (comment)

[martin-majlis-s1]

This is the line in dynatracer - https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/dynatraceexporter/metrics_exporter_test.go#L48
This is the line in dataset - https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/datasetexporter/logs_exporter_test.go#L276

I will stare on it tomorrow. I am not able to figure out, where it differs.

[martin-majlis-s1]

@mx-psi : I can remove/skip that test and then I can try to figure out, why is that test failing.

[songy23]

Please fix lint

[martin-majlis-s1]

My latest discovery is that it depends on the order. If the logs_exporter_test.go runs first, then it succeeds. When it's last, then it fails. Now I am trying to figure out why is this happening.

Succeeds:

go test -race -parallel 4 --tags="" ./logs_exporter_test.go ./datasetexporter_test.go logs_exporter.go  config.go datasetexporter.go traces_exporter.go factory.go factory_test.go traces_exporter_test.go config_test.go doc.go

Fails:

go test -race -parallel 4 --tags="" ./datasetexporter_test.go logs_exporter.go  config.go datasetexporter.go traces_exporter.go factory.go factory_test.go traces_exporter_test.go config_test.go doc.go ./logs_exporter_test.go 

EDIT: This comment is little bit misleading. In this code I have also removed the suite package. When I have removed the suite package back, it was failing again in any order.

[martin-majlis-s1]

So the final finding is that it's cause by the library - https://pkg.go.dev/github.com/stretchr/testify/suite. Once I have removed it - it started to work. It's no clear to me why.

[songy23]

LGTM