See https://dev.azure.com/ms/react-native-windows/_build/results?buildId=77100&view=logs&j=bd0c9a5d-cce5-5ddc-8479-a97ca35bf82d&t=384de848-3b6e-5843-d1fa-8f4d3a3f695b
This is seemingly fallout from #4765, since we see errors related to the new Microsoft.ReactNative.IntegrationTests project. This change doesn't appear in the changelog due to a change type of "none", so this build was the first time the publish pipeline did anything with it.
We're failing to bundle during the target added to do so.
MakeTestBundles:
npx --no-install react-native bundle --platform windows --entry-file d:\a\1\s\vnext\Microsoft.ReactNative.IntegrationTests\AddValues.js --bundle-output d:\a\1\s\vnext\target\x86\Debug\Microsoft.ReactNative.IntegrationTests\AddValues.bundle
Welcome to React Native!
Learn once, write anywhere
info Writing bundle output to:, d:\a\1\s\vnext\target\x86\Debug\Microsoft.ReactNative.IntegrationTests\AddValues.bundle
##[error]EXEC(0,0): Error ENOENT: no such file or directory, open 'd:\a\1\s\vnext\target\x86\Debug\Microsoft.ReactNative.IntegrationTests\AddValues.bundle'. Run CLI with --verbose flag for more details.
See https://dev.azure.com/ms/react-native-windows/_build/results?buildId=77100&view=logs&j=bd0c9a5d-cce5-5ddc-8479-a97ca35bf82d&t=384de848-3b6e-5843-d1fa-8f4d3a3f695b
This is seemingly fallout from #4765, since we see errors related to the new Microsoft.ReactNative.IntegrationTests project. This change doesn't appear in the changelog due to a change type of "none", so this build was the first time the publish pipeline did anything with it.
We're failing to bundle during the target added to do so.