aboutgitcodebugslistschat
path: root/test/lib
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2025-09-05 16:43:17 +1000
committerStefano Brivio <sbrivio@redhat.com>2025-09-05 13:00:20 +0200
commit00e3580ab925bbcaaaaefbb31e744fef84660937 (patch)
tree85285698a84b70dc2770831969147b9f9519743e /test/lib
parent3c44ef852586101eb6a5b8750d07454dbfb8a1a3 (diff)
downloadpasst-00e3580ab925bbcaaaaefbb31e744fef84660937.tar
passt-00e3580ab925bbcaaaaefbb31e744fef84660937.tar.gz
passt-00e3580ab925bbcaaaaefbb31e744fef84660937.tar.bz2
passt-00e3580ab925bbcaaaaefbb31e744fef84660937.tar.lz
passt-00e3580ab925bbcaaaaefbb31e744fef84660937.tar.xz
passt-00e3580ab925bbcaaaaefbb31e744fef84660937.tar.zst
passt-00e3580ab925bbcaaaaefbb31e744fef84660937.zip
test: Explicit specify forwarding ports for pasta in log rotation tests
test/pasta_options/log_to_file uses tcp_crr in a loop to generate log messages for what it's actually testing. For this to work, pasta needs to forward two ports. We set a PORTS variable with the options for this, but never actually use it. The test works, because without the options we use automatic port forwarding. That makes the test more fragile than it needs to be, in a way that's not at all related to what we're actually trying to test. Avoid this possible point of failure by explicitly specifying the forwarding. I encountered this because Fedora has now updated to a kernel with the /proc/net lseek() bug. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/lib')
0 files changed, 0 insertions, 0 deletions