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
The Universal Test X86 Release Fabric tests recently are failing more often and regularly than usual CI test issues. When they fail, they fail with the following error:
Failed Future2Test.Futureint_Then_DestroyLambdaAfterInvoke<Future2Test> [Futureint_Then_DestroyLambdaAfterInvoke] [2 ms]
Error Message:
Expected: [ isDestroyed ] is true
Actual: it is false
Line: 234
Stack Trace:
at futureTest.cpp:234 in D:\a\_work\1\s\vnext\Mso.UnitTests\future\futureTest.cpp:line 234
Currently, they're being resolved by just re-running the test until it passes.
Steps To Reproduce
Open a PR
Wait for test to fail on CI
Expected Results
No response
CLI version
npx @react-native-community/cli -v
Environment
npx @react-native-community/cli info
Community Modules
Test should pass on the first attempt.
Target Platform Version
None
Target Device(s)
No response
Visual Studio Version
None
Build Configuration
None
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered:
This started failing in the same timeline as the VS update. There was an agent update.
Failure rate on this is really high, so retries are... painful.
New agents are installing VS on a fresh image. The default versions we get may not match what folks are getting locally with non-fresh installs. We potentially would need to update to lock to an older version of VS if that's what's happening here.
This might result in an update to the dependency script.
@Yajur-Grover Can you confirm the VS version that's running in CI when this fails? We should cross reference with what people have locally to see if there's a version diff there.
Problem Description
The Universal Test X86 Release Fabric tests recently are failing more often and regularly than usual CI test issues. When they fail, they fail with the following error:
Currently, they're being resolved by just re-running the test until it passes.
Steps To Reproduce
Expected Results
No response
CLI version
npx @react-native-community/cli -v
Environment
npx @react-native-community/cli info
Community Modules
Test should pass on the first attempt.
Target Platform Version
None
Target Device(s)
No response
Visual Studio Version
None
Build Configuration
None
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: