-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Improve Http Telemetry tests #50226
Improve Http Telemetry tests #50226
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsReplace While I was changing the code, I added the asserts for Fixes #46075
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks. Hope it helps 😄
|
||
private static async Task WaitForEventCountersAsync(ConcurrentQueue<(EventWrittenEventArgs Event, Guid ActivityId)> events) | ||
{ | ||
DateTime startTime = DateTime.UtcNow; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DateTime startTime = DateTime.UtcNow; | |
long startTime = Environment.TickCount64; |
It might not matter here since the timeout is 30s, but every time I see DateTime
used like this, I'm a bit wary.
I misread the stack trace - there was only 1 failure on osx related to ordering. |
Replace
Task.Delay(hopefullyEnoughTime)
with actually waiting for event counters (following what we did in Sockets telemetry tests).While I was changing the code, I added the asserts for
ActivityId
s.Fixes #46075
Fixes #46073
Fixes #41723