Open jonthysell opened 4 days ago
I have confirmed that this hang can happen independent of the bundler hang addressed by https://github.com/microsoft/react-native-windows/pull/14063
See logs for an example of e2etest app hanging at .netnative way after bundler has completed successfully: https://dev.azure.com/ms/react-native-windows/_build/results?buildId=617132&view=logs&jobId=3559bc2f-1310-581e-5707-c6e64205ea8f&j=3559bc2f-1310-581e-5707-c6e64205ea8f&t=05b05db0-10ae-5c08-3d6e-0503fe2a7458
Problem Description
We're seeing a lot of PR / CI builds where the new project CLI tests fail for a old architecture C# X64 and/or ARM64 release build. The hang appears to happen during the .NET native step:
Debug builds don't have this problem for X86 and X64 because they don't use .Net Native. ARM64 on the other hand, requires .NetNative for all builds and is the most likely to hit this.
Steps To Reproduce
run-windows --release
Expected Results
No response
CLI version
15.0.0-alpha.2
Environment
info Fetching system and libraries information... System: OS: Windows 11 10.0.26100 CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz Memory: 5.20 GB / 15.84 GB Binaries: Node: version: 18.18.0 path: C:\Program Files\nodejs\node.EXE Yarn: version: 1.22.22 path: C:\Program Files (x86)\Yarn\bin\yarn.CMD npm: version: 9.8.1 path: C:\Program Files\nodejs\npm.CMD Watchman: Not Found SDKs: Android SDK: Not Found Windows SDK: AllowDevelopmentWithoutDevLicense: Enabled AllowAllTrustedApps: Enabled Versions:
Community Modules
No response
Target Platform Version
10.0.19041
Target Device(s)
Desktop
Visual Studio Version
Visual Studio 2022
Build Configuration
Release
Snack, code example, screenshot, or link to a repository
No response