-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test Failure System.Net.Http.Functional.Tests.TelemetryTest_Http20.EventSource_ConnectionPoolAtMaxConnections_LogsRequestLeftQueue #46073
Comments
Tagging subscribers to this area: @dotnet/ncl Issue Detailsfailed again in job: runtime-libraries-coreclr outerloop 20201214.1 failed test: System.Net.Http.Functional.Tests.TelemetryTest_Http20.EventSource_ConnectionPoolAtMaxConnections_LogsRequestLeftQueue net6.0-OSX-Release-x64-CoreCLR_release-OSX.1014.Amd64.Open Error message
Originally posted by @v-haren in #41723 (comment)
|
Failed again in run runtime-libraries-coreclr outerloop 20210209.3 Failed test:
Error message:
|
Failed again in runtime-libraries-coreclr outerloop 20210324.3 Failed test:
Error message:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This issue is still happening after PR #50226 (merged on 4/6), but only in PRs (during 3/11-4/6 the failures were in official builds only). Failures 4/7-6/25 (incl. PRs):
@MihaZupan should we reopen it or open a new issue, or do you think the PRs caused the failures? |
Hit in PR #51094 |
This specific issue is only appearing on OSX (non OSX failures are on release/preview branches that do not have changes from #50226). We can disable the test on OSX, though I don't see a reason as to why it would be failing in this manner. |
@MihaZupan one of the failures in the table is on Ubuntu ... |
…_LogsRequestLeftQueue test There is a unavoidable race condition between updating event counters and reading their values in WaitForEventCountersAsync. It waits for at least 2 sets of EventCounter event groups to ensure the last group is captured after any actual work (tests check that counters reset back to 0 if there is nothing happening). Since it looks for `requests-started` which occurs before `http11-requests-queue-duration` event, what it may see is only the tail of the last group and the start of the second, without waiting for a fresh `http11-requests-queue-duration`. In this, the assert `Assert.Equal(0, http11requestQueueDurations[^1])` on the line 549 will see a non-zero counter value and fail. This PR changes the condition to `< 3` to guarantee there is at least one full group of events in the window. Co-authored by @MihaZupan Fixes #46073
…_LogsRequestLeftQueue test (#55729) There is a unavoidable race condition between updating event counters and reading their values in WaitForEventCountersAsync. It waits for at least 2 sets of EventCounter event groups to ensure the last group is captured after any actual work (tests check that counters reset back to 0 if there is nothing happening). Since it looks for `requests-started` which occurs before `http11-requests-queue-duration` event, what it may see is only the tail of the last group and the start of the second, without waiting for a fresh `http11-requests-queue-duration`. In this, the assert `Assert.Equal(0, http11requestQueueDurations[^1])` on the line 549 will see a non-zero counter value and fail. This PR changes the condition to `< 3` to guarantee there is at least one full group of events in the window. Co-authored by @MihaZupan Fixes #46073
failed again in job: runtime-libraries-coreclr outerloop 20201214.1
failed test: System.Net.Http.Functional.Tests.TelemetryTest_Http20.EventSource_ConnectionPoolAtMaxConnections_LogsRequestLeftQueue
net6.0-OSX-Release-x64-CoreCLR_release-OSX.1014.Amd64.Open
Error message
Originally posted by @v-haren in #41723 (comment)
The text was updated successfully, but these errors were encountered: