This issue is somewhat similar to CSIT-1936 but happens very rarely. Or perhaps it only rarely leads to test failure, as 64B test cases are likely to pass even with wrong bandwidth.

One occurrence [0], only one test case affected (Intel-x520 and dpdk plugin):
trex.common.trex_exceptions.TRexError: Port 0 : *** Expected L1 B/W: '8.73783 Gbps' exceeds port line rate: '1 Gbps'
Another occurrence [1], all test cases in the suite are affected (Intel-e810cq and AVF plugin):
trex.common.trex_exceptions.TRexError: Port 0 : *** Expected L1 B/W: '96.608 Gbps' exceeds port line rate: '50 Gbps'

[0] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-iterative-2310-3n-tsh/20/log.html.gz#s1-s1-s1-s1-s6-t5-k2-k13-k9-k10-k1-k1-k1-k11
[1] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-report-iterative-2310-3nb-spr/28/log.html.gz#s1-s1-s1-s1-s4-t1-k2-k13-k14