If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Error when using clang on jenkins1.qa.scl3

NEW
Unassigned

Status

Testing
WebQA
2 years ago
2 years ago

People

(Reporter: Eli, Unassigned)

Tracking

Version 3
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
When trying to install a particular npm package for our performance testing automation job, it goes through some set up which underneath uses clang. This process works just fine on the child nodes, which use Ubuntu, but this doesn't work on the master node, which I believe runs Fedora.

Log:

+ npm install '@mozilla/raptor@^5.0.0'


> sockit-to-me@1.0.2 install /var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me
> CC=clang CXX=clang++ node-gyp configure build --verbose

gyp info it worked if it ends with ok
gyp verb cli [ '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node.js_4.2.2/bin/node',
gyp verb cli   '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node.js_4.2.2/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'configure',
gyp verb cli   'build',
gyp verb cli   '--verbose' ]
gyp info using node-gyp@3.0.3
gyp info using node@4.2.2 | linux | x64
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /usr/bin/python2
gyp verb check python version `python2 -c "import platform; print(platform.python_version());"` returned: "2.6.6\n"
gyp verb get node dir no --target version specified, falling back to host node version: 4.2.2
gyp verb command install [ '4.2.2' ]
gyp verb install input version string "4.2.2"
gyp verb install installing version: 4.2.2
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 4.2.2
gyp verb build dir attempting to create "build" dir: /var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me/build
gyp verb build dir "build" dir needed to be created? null
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: /var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me/build/config.gypi
gyp verb config.gypi checking for gypi file: /var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me/config.gypi
gyp verb common.gypi checking for gypi file: /var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me/common.gypi
gyp verb gyp gyp format was not specified; forcing "make"
gyp info spawn python2
gyp info spawn args [ '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node.js_4.2.2/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node.js_4.2.2/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/var/lib/jenkins/.node-gyp/4.2.2/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/var/lib/jenkins/.node-gyp/4.2.2',
gyp info spawn args   '-Dnode_gyp_dir=/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node.js_4.2.2/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args   '-Dmodule_root_dir=/var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir /var/lib/jenkins/.node-gyp/4.2.2
gyp verb `which` succeeded for `make` /usr/bin/make
gyp info spawn make
gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory `/var/lib/jenkins/jobs/perf.coldlaunch.flame-kk.512/workspace/node_modules/@mozilla/raptor/node_modules/raptor-test/node_modules/sockit-to-me/build'
  clang++ '-DNODE_GYP_MODULE_NAME=sockit' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' -I/var/lib/jenkins/.node-gyp/4.2.2/include/node -I/var/lib/jenkins/.node-gyp/4.2.2/src -I/var/lib/jenkins/.node-gyp/4.2.2/deps/uv/include -I/var/lib/jenkins/.node-gyp/4.2.2/deps/v8/include  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++0x -MMD -MF ./Release/.deps/Release/obj.target/sockit/src/addon.o.d.raw  -c -o Release/obj.target/sockit/src/addon.o ../src/addon.cc
In file included from ../src/addon.cc:2:
In file included from /var/lib/jenkins/.node-gyp/4.2.2/include/node/node.h:42:
/var/lib/jenkins/.node-gyp/4.2.2/include/node/v8.h:18:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
(Reporter)

Comment 1

2 years ago
Just to clarify, the issue occurs on the master node itself, jenkins1.qa.scl3.mozilla.com, not the child nodes.
You need to log in before you can comment on or make changes to this bug.