]> git.ipfire.org Git - thirdparty/rspamd.git/commit
[Test] 411_logging: read per-suite rspamd output, not global .last
authorVsevolod Stakhov <vsevolod@rspamd.com>
Mon, 25 May 2026 20:00:43 +0000 (21:00 +0100)
committerVsevolod Stakhov <vsevolod@rspamd.com>
Mon, 25 May 2026 20:00:43 +0000 (21:00 +0100)
commit640e672dbbfd54839b1798148432d42eb48df552
treece38efae1043894897e92d66d6160143cc4f5594
parent040ee842059a96218a40d421284b881a08670671
[Test] 411_logging: read per-suite rspamd output, not global .last

save_run_results writes each rspamd's logs to two destinations: the
stable per-suite/per-test directory under robot-save/, and a global
robot-save/<file>.last "convenience" copy of the most recent run.

The three 411_logging tests asserted on the .last copies. Under
pabot another worker can teardown -- and overwrite the .last files
-- between this suite's Rspamd Teardown saving them and the
assertion reading them, so the assertion ends up running against a
different suite's rspamd output and matching the wrong format.

Switch to the per-suite paths
(robot-save/${SUITE_NAME}/rspamd.stderr for the console suites,
robot-save/${SUITE_NAME}/${TEST_NAME}/rspamd.log for the JSON file
test). Those paths aren't shared across pabot workers.

Local: three back-to-back parallel runs of the 411_logging
directory pass 3/3 each time.
test/functional/cases/411_logging/000_console/000_systemd_logger.robot
test/functional/cases/411_logging/000_console/001_timestamps.robot
test/functional/cases/411_logging/001_file/000_json.robot