-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Try synchronizing dispose and output #20341
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
Conversation
@@ -27,6 +27,7 @@ public InteropTests(ITestOutputHelper output) | |||
} | |||
|
|||
[Theory] | |||
[Repeat] |
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.
Runs 10 times which should take an extra 20 mins.
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.
You'll run the PR build a few times with this and then remove it before checking in, right?
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.
That's the plan.
Didn't we have a PR that fixed this by booting up the server per test.? |
Yea last time I saw
So I thought the server was logging in between tests, which I still think occured, which is why I converted to booting and shutting down a server per test. However, today @Tratcher pointed to a build that still failed and after looking at it, it seems like the server was logging after shutting down which can also cause this error. I've also added TL:DR my fix was insufficient. Hopefully this makes it more reliable. |
What about explicitly unregistering test output logging from the processes in dispose? |
ProcessEx already does that, but still seems to be hitting a race. |
@@ -27,6 +27,7 @@ public InteropTests(ITestOutputHelper output) | |||
} | |||
|
|||
[Theory] | |||
[Repeat] |
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.
You'll run the PR build a few times with this and then remove it before checking in, right?
/azp run Tests: Helix x64 |
No pipelines are associated with this pull request. |
/azp run aspnetcore-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
40 runs no failure, I think that's sufficient to declare this battle won. |
@anurse should test flakiness improvements like this go into preview3? |
Try resolving #20336 with more synchronization.