You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assert.AreEqual(2,rsb.Tokens.Count,"Unexpected tokens count after load.");
Both involving adding new tokens.
This seems to more often happen for WinUI 3, so possibly has to do with different behavior or regression there? But something definitely seems to be wonky and unstable here with this control and these tests.
Steps to reproduce
Intermittent test failure
Expected behavior
Tokens always added
Screenshots
No response
Code Platform
UWP
WinAppSDK / WinUI 3
Web Assembly (WASM)
Android
iOS
MacOS
Linux / GTK
Windows Build Number
Windows 10 1809 (Build 17763)
Windows 10 1903 (Build 18362)
Windows 10 1909 (Build 18363)
Windows 10 2004 (Build 19041)
Windows 10 20H2 (Build 19042)
Windows 10 21H1 (Build 19043)
Windows 10 21H2 (Build 19044)
Windows 10 22H2 (Build 19045)
Windows 11 21H2 (Build 22000)
Other (specify)
Other Windows Build number
No response
App minimum and target SDK version
Windows 10, version 1809 (Build 17763)
Windows 10, version 1903 (Build 18362)
Windows 10, version 1909 (Build 18363)
Windows 10, version 2004 (Build 19041)
Windows 10, version 2104 (Build 20348)
Windows 11, version 22H2 (Build 22000)
Other (specify)
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.
The text was updated successfully, but these errors were encountered:
Describe the bug
At least some part of #347 seem to be intermittent failures in the RichSuggestBox tests as well
Here:
Windows/components/RichSuggestBox/tests/Test_RichSuggestBox.cs
Line 143 in 2c0f9b3
And here:
Windows/components/RichSuggestBox/tests/Test_RichSuggestBox.cs
Line 308 in 2c0f9b3
Both involving adding new tokens.
This seems to more often happen for WinUI 3, so possibly has to do with different behavior or regression there? But something definitely seems to be wonky and unstable here with this control and these tests.
Steps to reproduce
Expected behavior
Tokens always added
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.
The text was updated successfully, but these errors were encountered: