test: fix parallel/test-setproctitle.js on alpine

[DavidCai1111]

Fixes: #12399

As mentioned in the ref issue, since Busybox ps does not support -p switch, using ps -o and grep instead to get the process title and then check it.

The title variable in this test script was also renamed from 'testme' to 'test', because it seems that on alpine if trying to set the process title to a string whose length is >=5 like 'abcde', it will become {abcde} abcd in ps output:

> docker run -it node:alpine
> process.title = 'abcde'
'abcde'
> child_process.execSync('ps').toString().split('\n')
[ 'PID   USER     TIME   COMMAND',
  '    1 root       0:00 {abcde} abcd',
  '   20 root       0:00 /bin/sh -c ps',
  '   21 root       0:00 ps',
  '' ]

> docker run -it node:alpine
> process.title = 'abcd'
'abcd'
> child_process.execSync('ps').toString().split('\n')
[ 'PID   USER     TIME   COMMAND',
  '    1 root       0:00 abcd',
  '   20 root       0:00 /bin/sh -c ps',
  '   21 root       0:00 ps',
  '' ]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

Affected core subsystem(s)

test

[vsemozhetbyt]

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

[benjamingr]

This breaks on FreeBSD apparently:

not ok 945 parallel/test-setproctitle
  ---
  duration_ms: 0.370
  severity: fail
  stack: |-
    assert.js:554
    assert.ifError = function ifError(err) { if (err) throw err; };
                                                      ^
    
    Error: Command failed: ps -o pid,args= | grep '^\s*4180 test'
    
        at ChildProcess.exithandler (child_process.js:247:12)
        at emitTwo (events.js:125:13)
        at ChildProcess.emit (events.js:213:7)
        at maybeClose (internal/child_process.js:882:16)
        at Socket.<anonymous> (internal/child_process.js:335:11)
        at emitOne (events.js:115:13)
        at Socket.emit (events.js:210:7)
        at Pipe._handle.close [as _onclose] (net.js:531:12)

---

Ping @nodejs/build regarding CI failures:

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

https://ci.nodejs.org/job/node-test-commit-osx/9018/nodes=osx1010/console

[lpinca]

@benjamingr

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

This shouldn't be an issue.

[gibfahn]

@benjamingr the xcodebuild warnings aren't an issue (see nodejs/node-gyp#1057) xcodebuild is called twice but never actually used.

[jasnell]

There are definite failures in CI with this that need looking at

[DavidCai1111]

Updated, and CI looks good now 😃

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

[DavidCai1111]

Landed in ee0620b

[gibfahn]

Doesn't backport cleanly for me to v6.x, would you be willing to backport? If yes please follow the guide and raise a backport PR, if no let me know or add the dont-land-on label.

[DavidCai1111]

@gibfahn Yeah...Backport PR: #13072