build: add missing comma in sources list

[danbev]

This commit adds a missing comma in the sources list. This effects at
least window which produces the following warning where trace_event.h
and src/util.h are concatenated:

Warning: Missing input files:src\tracing\trace_event.hsrc\util.h

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

build

[danbev]

CI: https://ci.nodejs.org/job/node-test-pull-request/11091/

[gireeshpunathil]

I wonder how it was building / working so far with this issue!

[danbev]

Triggering another CI to double check Windows failure: https://ci.nodejs.org/job/node-test-pull-request/11125/

[danbev]

Rebased CI: https://ci.nodejs.org/job/node-test-pull-request/11127/

[danbev]

test/arm-fanned failure looks unrelated

console output:

warning: failed to remove out/Removing out/Build step 'Execute shell' marked build as failureTAP Reports Processing: STARTLooking for TAP results report in workspace using pattern: *.tapDid not find any matching files. Setting build result to FAILURE.Checking ^not okJenkins Text Finder: File set '*.tap' is emptyNotifying upstream projects of job completionFinished: FAILURE

test/windows-fanned failure looks unrelated

console output:

Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10[node-test-binary-windows] $ cmd /c call C:\Users\ADMINI~1\AppData\Local\Temp\1\jenkins4777955810906737101.batc:\workspace\node-test-binary-windows>echo off Wed 11/01/2017 4:03:40.35c:\workspace\node-test-binary-windows>tasklist | grep node || truec:\workspace\node-test-binary-windows>exit 0 [node-test-binary-windows] $ cmd /c call C:\Users\ADMINI~1\AppData\Local\Temp\1\jenkins2702603836202563709.batc:\workspace\node-test-binary-windows>TASKKILL /F /IM node.exe /T || TRUEERROR: The process "node.exe" not found.c:\workspace\node-test-binary-windows>TASKKILL /F /IM cctest.exe /T || TRUEERROR: The process "cctest.exe" not found.c:\workspace\node-test-binary-windows>TASKKILL /F /IM run-tests.exe /T || TRUEERROR: The process "run-tests.exe" not found.c:\workspace\node-test-binary-windows>TASKKILL /F /IM yes.exe /T || TRUEERROR: The process "yes.exe" not found.c:\workspace\node-test-binary-windows>git checkout -f refs/remotes/jenkins_tmp/jenkins-node-test-commit-windows-fanned-13053-binary-windows/win-vs2013 error: pathspec 'refs/remotes/jenkins_tmp/jenkins-node-test-commit-windows-fanned-13053-binary-windows/win-vs2013' did not match any file(s) known to git.c:\workspace\node-test-binary-windows>if 1 NEQ 0 exit /b 1 Build step 'Execute Windows batch command' marked build as failureTAP Reports Processing: STARTLooking for TAP results report in workspace using pattern: *.tapDid not find any matching files. Setting build result to FAILURE.Checking ^not okJenkins Text Finder: File set '*.tap' is emptyNotifying upstream projects of job completionFinished: FAILURE

[danbev]

Landed in 18df171

[refack]

I wonder how it was building / working so far with this issue!

Since these are .h files they are only used for change tracking, they are not actually compiled.
But this might explain why MSBuild is sometimes too eager to rebuild - because one of the files it's tracking will never exist.