Flaky Test - windows-msi

[djaglowski]

This check fails frequently, without much information. Example.

Run .\internal\buildscripts\packaging\msi\make.ps1 Confirm-MSI
  .\internal\buildscripts\packaging\msi\make.ps1 Confirm-MSI
  shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
  env:
    TEST_RESULTS: testbed/tests/results/junit/results.xml
Error: The operation was canceled.

As far as I can tell, the operation is not typically canceled intentionally. Possibly it is due to a resource being reallocated, but otherwise this would appear to be a bug.

---

I would like to re-establish whether we actually want to have this check at all. We do not currently produce an MSI in the releases repo. @open-telemetry/collector-contrib-approvers, any opinions on whether this check is really necessary?

[dmitryax]

I think this test is important enough to have. It verifies the full cycle of collector service on Windows. It may be a bug in the make.ps1 script that should be fixed.

Can we skip the test for now as we did we other flaky tests?

[djaglowski]

Seems reasonable. I'll open a new PR that skips the job.

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

[pjanotti]

Notice that core repo currently has a test to validate the collector running as a Windows service, see open-telemetry/opentelemetry-collector#9726