What to do if your CL broke the Node.js integration build

Node.js uses V8 stable or beta. For additional integration, the V8 team builds Node with V8's main branch, i.e., with a V8 version from today. We provide an integration bot for Linux, while Windows and Mac are in the works.

If the node_ci_linux64_rel bot fails on the V8 commit queue, there is either a legitimate problem with your CL (fix it) or Node must be modified. If the Node tests failed, search for “Not OK” in the log files. This document describes how to reproduce the problem locally and how to make changes to V8’s Node fork if your V8 CL causes the build to fail.

Source #

Follow the instructions at the node-ci repository to check out source.

Test changes to V8 #

V8 is set up as a DEPS dependency of node-ci. You may want to apply changes to V8 for testing or to reproduce failures. To do so, add your main V8 checkout as remote:

cd v8
git remote add v8 <your-v8-dir>/.git
git fetch v8
git checkout v8/<your-branch>
cd ..

Remember to run gclient hooks before compiling.

gclient runhooks
JOBS=`nproc` make test

Make changes to Node.js #

Node.js is also set up as a DEPS dependency of node-ci. You may want to apply changes to Node.js to fix breakages that V8 changes may cause. V8 tests against a fork of Node.js. You need a GitHub account to make changes to that fork.

Get the Node sources #

Fork V8’s Node.js repository on GitHub (click the fork button) unless you already did previously.

Add your both your fork and V8’s fork as remotes to the existing checkout:

cd node
git remote add v8 http://github.com/v8/node
git remote add <your-user-name> git@github.com:<your-user-name>/node.git
git fetch v8
git checkout v8/node-ci-<sync-date>
export BRANCH_NAME=`date +"%Y-%m-%d"`_fix_name
git checkout -b $BRANCH_NAME

Note <sync-date> is the date we sync’ed with upstream Node.js. Choose the latest date.

Make your changes to the Node.js checkout, and commit them. Then push the changes to GitHub:

git push <your-user-name> $BRANCH_NAME

And create a pull request against the branch node-ci-<sync-date>.

Once the pull request has been merged to V8’s fork of Node.js, you need to update node-ci’s DEPS file, and create a CL.

git checkout -b update-deps
gclient setdep --var=node_revision=<merged-commit-hash>
git add DEPS
git commit -m 'Update Node'
git cl upload