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

EventLogContainer Index is out of bounds #4873

Open
hankweber opened this issue Jan 31, 2024 · 1 comment
Open

EventLogContainer Index is out of bounds #4873

hankweber opened this issue Jan 31, 2024 · 1 comment

Comments

@hankweber
Copy link

hankweber commented Jan 31, 2024

Description

We are currently running into an issue running vstest in ADO pipelines where the runs will execute all of our tests, but then wait because ADO hasn't received data about all tests. We have telemetry and logs that make us believe that test execution is actually completing but then something in VSTest is preventing the results from being sent to ADO. When looking into some logs we found that the EventLogCollector/Container is repeatedly hitting an Index is out of bounds issue during the OnTestSessionEnd event until the test session times out.

Steps to reproduce

This issue doesn't repro 100% of the time. We usually hit the issue a few times a day out of 100s of runs.

Expected behavior

Test session should end successfully.

Actual behavior

Test session continues indefinitely due to the EventLogDataCollector hitting an error.

Diagnostic logs

Slice-Execution-29529552_vwn0nr.datacollector.24-01-26_23-44-45_57554_6-SHORT.txt - NOTE: the exception on line 18769 happens repeatedly until our test session times out and the original diag file repeats this error for 4+ hrs. I cut out the repeated errors to trim down file size.

Slice-Execution-29572449_t1fmhp.datacollector.24-02-01_01-42-10_22148_6-Good_Example.txt - Example from a run where we do not experience the issue

Environment

OS: Windows 11
vstest: 17.8

@nohwnd
Copy link
Member

nohwnd commented Feb 2, 2024

I see there is real problem with the logger. It tries to handle the clearing of the log, but does not do it correctly and so the underlying "windows" api throws.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants