-
Notifications
You must be signed in to change notification settings - Fork 984
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
ToolStrip tests is flaky in arm64 and x86 CI build #6610
Comments
Related Issue dotnet#6610 and Issue dotnet#6654 These tests fail sometimes in x86 CI build, that blocks deployment of fixes into sdk.
|
These tests sometimes fail in CI and block deployment. Related issues: dotnet#6610, dotnet#6714, dotnet#6739, dotnet#6926
These tests sometimes fail in CI and block deployment. Related issues: dotnet#6610, dotnet#6714, dotnet#6739, dotnet#6926
These tests sometimes fail in CI and block deployment. Related issues: dotnet#6610, dotnet#6714, dotnet#6739, dotnet#6926
ToolStrip_WndProc_InvokeMouseActivateWithHandle_Success does not show among failures in https://runfo.azurewebsites.net/search/tests/?q=started%3A%7E14+definition%3A267. Thus closing |
Never mind, they don't show up in the stats because they are disabled. |
related: #7333 |
Also have seen failures on x64. The test is supposed to return zero, but the docs don't say anything about that value. |
.NET Core Version: 7.0
Have you experienced this same bug with .NET Framework?: No
Problem description:
ToolStrip_WndProc_InvokeMouseActivateWithHandle_Success
unit test fails sometime in arm64 CI build for successful PRs, that blocking deployment of fixes into sdk. Stack trace (System.Windows.Forms.Tests_net7.0_arm64.log):ToolStrip_WndProc_InvokeMouseActivate_Success
:Expected behavior:
All correct tests pass every time.
Minimal repro:
The text was updated successfully, but these errors were encountered: