parallel/test-tick-processor.js fails on ARM

[brendanashworth]

Just got this failure on an unrelated test change PR:

not ok 672 - test-tick-processor.js
# nm: /lib/arm-linux-gnueabihf/ld-2.13.so: no symbols
# nm: '[sigpage]': No such file
# nm: /lib/arm-linux-gnueabihf/libdl-2.13.so: no symbols
# nm: /lib/arm-linux-gnueabihf/librt-2.13.so: no symbols
# nm: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.19: no symbols
# nm: /lib/arm-linux-gnueabihf/libm-2.13.so: no symbols
# nm: /lib/arm-linux-gnueabihf/libgcc_s.so.1: no symbols
# nm: /lib/arm-linux-gnueabihf/libc-2.13.so: no symbols
# nm: '[vectors]': No such file
# 
# assert.js:89
# throw new assert.AssertionError({
# ^
# AssertionError: null == true
# at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/nodes/armv7-wheezy/test/parallel/test-tick-processor.js:27:1)
# at Module._compile (module.js:430:26)
# at Object.Module._extensions..js (module.js:448:10)
# at Module.load (module.js:355:32)
# at Function.Module._load (module.js:310:12)
# at Function.Module.runMain (module.js:471:10)
# at startup (node.js:117:18)
# at node.js:952:3

It passed in the original PR CI run, so it may be flaky.

cc @matthewloring

[matthewloring]

Yea, seems like flakiness. I was able to test with windows/mac/linux but I don't have an arm machine. I'll try to get my hands on one and figure out what's happening.

[rvagg]

that's a scaleway machine and they are going through some storage upgrades right now, I'm pretty confident we hit something funky with the timing of this run

[brendanashworth]

ok, thanks!