Make pathfinder INFO line counting non-failing unconditionally.

[rwgk]

This resolves failures in the nightly testing.

Super-simple alternative to to #1592 and #1593

The INFO lines are very valuable in the unique situation that pathfinder is in: the behavior is by design highly dependent on the environment setup. Without the INFO lines, we have no way of validating what the behavior is in the GHA jobs.

The fraction of INFO lines in a typical CI log file is around 2.5%:

rwgk-win11.localdomain:~/wrk/logs_21965469504 $ wc -l Test_linux-aarch64___py3.11__12.9.1__wheels__a100.txt
5596 Test_linux-aarch64___py3.11__12.9.1__wheels__a100.txt
rwgk-win11.localdomain:~/wrk/logs_21965469504 $ grep 'Z INFO' Test_linux-aarch64___py3.11__12.9.1__wheels__a100.txt | wc -l
140

In interactive use, the INFO lines are shown only if the pytest -v option is specified. In that case, the fraction of INFO lines in the combined pathfinder, bindings, core test outputs is also around 2%, e.g.:

smc120-0009.ipp2a2.colossus.nvidia.com:/wrk/logs $ wc -l cuda-python_qa_bindings_linux_2026-01-07+142305_tests_log.txt
3199 cuda-python_qa_bindings_linux_2026-01-07+142305_tests_log.txt
smc120-0009.ipp2a2.colossus.nvidia.com:/wrk/logs $ grep -a '^INFO ' cuda-python_qa_bindings_linux_2026-01-07+142305_tests_log.txt | wc -l
55

(The exact fraction here is 1.7%, but the log file includes some other things, like nvidia-smi, pip list.)

[copy-pr-bot]

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[rwgk]

/ok to test

[cpcloud]

I made #1593 for a reason. It's a huge nuisance for the common case of an initial "what went wrong here" workflow to have bunch of log spam in CI. It wasn't designed to solve the nightly problem, it was designed to solve another problem, so it's not an alternative to anything.

[cpcloud]

Using standard logging facilities instead of what I would consider a weird list appending function is also just easier to follow IMO.

[cpcloud]

Again, I'm not trying to remove the INFO lines, I'm trying to make the common CI debugging case less spammy, and keep the INFO lines around for any subsequent deeper dives.

[rwgk]

Again, I'm not trying to remove the INFO lines, I'm trying to make the common CI debugging case less spammy, and keep the INFO lines around for any subsequent deeper dives.

Can we please keep the INFO mechanism as is for now and go with this easy solution that unblocks you?

The other PRs are different, but not simplifications.

The separate file has a bunch of pitfalls and I'd have to make adjustments elsewhere (e.g. extra steps to get them into ctk-next qa logs). I'd appreciate if we don't have to tear up the road for the small issue you stumbled over.

[rwgk]

There was a known flake:

https://github.com/NVIDIA/cuda-python/actions/runs/21995912807/job/63556542405?pr=1621

Tracked now under #1622

[github-actions]

Doc Preview CI
Preview removed because the pull request was closed or merged.