Sometimes TRex says [0] "trex.common.trex_exceptions.TRexError: action requires at least one port", or even [1] "trex.common.trex_exceptions.TRexError: Port 1 : *** please acquire the port before modifying port state".
Sometimes VPP says [2] "Interfaces still not in link-up state: ['TwentyFiveGigabitEthernet89/0/2']".
There may be other symptoms, depending on test type and exact time the issue happens.

In past, we have seen similar issues on other testbed, that got fixed by connecting the cable properly, but even then the failures were not very frequent.

On 3n-icx (both of them), the failing tests actually outnumber the passing ones. As the frequency is similar, maybe the issue is not in nic/cable but in driver?
Either way, whis does not look like a VPP (or CSIT or TRex) issue.

[0] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-iterative-2406-3n-icxd/58/log.html.gz#s1-s1-s1-s1-s18-t2-k2-k11-k9-k13-k9-k2
[1] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-iterative-2406-3n-icxd/58/log.html.gz#s1-s1-s1-s1-s18-t1-k2-k11-k9-k13-k7-k2
[2] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-iterative-2406-3n-icxd/58/log.html.gz#s1-s1-s1-s1-s18-t6-k2-k6-k3-k2-k1