test: skip C++ symbols in tick-processor-arguments

[pipobscure]

test/parallel/test-tick-processor-arguments only checks that a CLI flag (--preprocess) is passed through to the V8 tick processor. Processing a --prof log, however, makes the tick processor resolve the C++ symbols of every shared library listed in the log by shelling out to nm once per library (and, in Node's polyfill, piping the result through c++filt again on macOS).

On the x86_64-darwin: with shared libraries GitHub Actions job, node links roughly a hundred dylibs (V8 split into eight libraries, ~85 abseil libraries, ICU, libuv, ...), so a single --prof-process run spawns a couple of hundred external processes on a slow Intel runner and exceeds the 120s test timeout. It has done so on unrelated PRs, e.g. https://github.com/nodejs/node/actions/runs/34138185061/job/101794526205 and https://github.com/nodejs/node/actions/runs/34169515699. The outcome of the test also depends on the host toolchain (nm availability, Xcode license state) rather than on node itself; #50050 was a different symptom of the same dependency.

This drops the shared-library, entries from the log before handing it to --prof-process, so the test exercises argument handling only. The log remains a valid V8 log and the output is still checked to be valid JSON. C++ symbol resolution is covered by the tests in test/tick-processor.

Measured locally on Linux (static build):

variant	wall time	processes spawned by --prof-process
before	~630 ms	649 (408 of them nm)
after	~170 ms	1

The SmartOS SKIP entry in parallel.status is left as is; I cannot verify whether the address-range problem from #50050 is confined to the shared-library lines.

Refs: #50050

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.16%. Comparing base (2987a59) to head (bdec92d).
⚠️ Report is 41 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #65906   +/-   ##
=======================================
  Coverage   90.16%   90.16%           
=======================================
  Files         771      771           
  Lines      265097   265097           
  Branches    50358    50355    -3     
=======================================
+ Hits       239026   239031    +5     
- Misses      17011    17022   +11     
+ Partials     9060     9044   -16     

see 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[MikeMcC399]

https://github.com/nodejs/node/actions/workflows/test-shared.yml?query=is%3Afailure+is%3Atimed_out

shows multiple workflows failing with timeout, for instance https://github.com/nodejs/node/actions/runs/34212576163 from @panva

x86_64-darwin: with shared libraries / build: test/parallel/test-tick-processor-arguments.js#L0
Command: out/Release/node /Users/runner/work/_temp/node-v27.0.0-nightly2026-09-081b200078a0-slim/test/parallel/test-tick-processor-arguments.js
--- TIMEOUT ---

so this PR does deserve attention!

[pipobscure]

Can someone please request-ci for me please!

[MikeMcC399]

Can someone please request-ci for me please!

It needs a technical review of your PR and at least one approval before request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. will be accepted.

[mcollina]

lgtm

[pipobscure]

Yikes! What's happening here?

[nodejs-github-bot]

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

Edit: this was aborted by the Releasers Team due to release priorities. I submitted a new request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. to start afresh

I would really like to see this PR succeed, as I'm seeing CI fail in multiple other PRs and re-running the CI often just repeats the issue.

[pipobscure]

Yikes! What happened there?

[MikeMcC399]

I didn't realise that the commit queue is still disabled, so to avoid confusion, I've removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label, and I've leave @panva to continue here.