Skip to content

test: log MSBuild output on Windows build failures#3328

Open
legendecas wants to merge 1 commit into
nodejs:mainfrom
legendecas:debug/win-node26-ci-logging
Open

test: log MSBuild output on Windows build failures#3328
legendecas wants to merge 1 commit into
nodejs:mainfrom
legendecas:debug/win-node26-ci-logging

Conversation

@legendecas

@legendecas legendecas commented Jun 9, 2026

Copy link
Copy Markdown
Member
Checklist
  • npm install && npm run lint && npm test passes
  • tests are included
  • documentation is changed or added
  • commit message follows commit guidelines
Description of change

Refs: #3327

@legendecas

Copy link
Copy Markdown
Member Author

The error seems to be:

  LINK : fatal error LNK1117: syntax error in option 'opt:lldltojobs=2' [D:\a\node-gyp\node-gyp\test\node_modules\hello_world\build\hello.vcxproj]

    20 Warning(s)
    1 Error(s)

@StefanStojanovic

Copy link
Copy Markdown
Contributor

From what I understand, the idea behind this draft PR is that you wanted to see what the problem was with Node.js v26 tests on Windows. The question I have is, do we want to keep this change to be able to get more information in the future or would that not be useful to have?

@legendecas

Copy link
Copy Markdown
Member Author

From what I understand, the idea behind this draft PR is that you wanted to see what the problem was with Node.js v26 tests on Windows. The question I have is, do we want to keep this change to be able to get more information in the future or would that not be useful to have?

Yes, I think this is generally helpful and worth to keep.

@legendecas legendecas force-pushed the debug/win-node26-ci-logging branch from ff52fd5 to b9e5386 Compare June 10, 2026 21:08
@legendecas legendecas force-pushed the debug/win-node26-ci-logging branch from b9e5386 to f50be52 Compare June 10, 2026 21:10
@legendecas legendecas marked this pull request as ready for review June 10, 2026 21:10
@legendecas legendecas changed the title test: log MSBuild output and cache dir on Windows build failures test: log MSBuild output on Windows build failures Jun 10, 2026

@cclauss cclauss left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix order of return values.

Comment thread test/test-addon.js

const execFile = async (cmd) => {
const [err,, stderr] = await util.execFile(process.execPath, cmd, {
const [err, stdout, stderr] = await util.execFile(process.execPath, cmd, {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Err, out, err != …

Comment thread test/test-addon.js
encoding: 'utf-8'
})
return [err, stderr.toString().trim().split(/\r?\n/)]
return [err, stderr.toString().trim().split(/\r?\n/), stdout.toString().trim()]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Err, err, out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants