Version
nightly
Platform
Windows
Subsystem
No response
What steps will reproduce the bug?
Windows CI builds are failing.
How often does it reproduce? Is there a required condition?
Today's daily master build and a number of CI's for pull requests.
What is the expected behavior?
Build completes.
What do you see instead?
Build fails. e.g. https://ci.nodejs.org/job/node-compile-windows/45207/nodes=win-vs2019/console
08:23:37 )
08:23:37 tools\license2rtf.mjs 0<LICENSE 1>Release\license.rtf
08:23:37 ) else (Release\node.exe tools\license2rtf.mjs 0<LICENSE 1>Release\license.rtf )
08:23:37
08:23:37 > if errorlevel 1 echo Failed to generate license.rtf & goto exit
08:23:37 Failed to generate license.rtf
08:23:37
08:23:37 > if 13 NEQ 0 exit /b 13
08:23:37
08:23:37 > if errorlevel 1 exit /b
08:23:37
08:23:37 > if errorlevel 1 exit /b
08:23:37
08:23:37 > if errorlevel 1 exit /b
08:23:37
08:23:37 > if errorlevel 1 exit /b
08:23:37 Build step 'Execute Windows batch command' marked build as failure
Additional information
#43101 landed yesterday and looks very relevant. That passed its CI but maybe something else has landed that when combined causes the break?
cc @nodejs/platform-win
Version
nightly
Platform
Windows
Subsystem
No response
What steps will reproduce the bug?
Windows CI builds are failing.
How often does it reproduce? Is there a required condition?
Today's daily master build and a number of CI's for pull requests.
What is the expected behavior?
Build completes.
What do you see instead?
Build fails. e.g. https://ci.nodejs.org/job/node-compile-windows/45207/nodes=win-vs2019/console
Additional information
#43101 landed yesterday and looks very relevant.
That passed its CI but maybe something else has landed that when combined causes the break?cc @nodejs/platform-win