[LTP] LTP in valgrind :)

[Cyril Hrubis]

Hi!
> That looks pretty interesting, I just tried it and it turns:
> 
> $ ./testcases/kernel/syscalls/dup/dup01 
> tst_tmpdir.c:316: TINFO: Using /tmp/LTP_dupbmNNGn as tmpdir (tmpfs filesystem)
> tst_test.c:1907: TINFO: LTP version: VALGRIND_3_25_0-10-g0ce068434ec3
> tst_test.c:1911: TINFO: Tested kernel: 6.13.11-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 10 19:02:09 UTC 2025 x86_64
> tst_kconfig.c:88: TINFO: Parsing kernel config '/lib/modules/6.13.11-200.fc41.x86_64/build/.config'
> tst_test.c:1729: TINFO: Overall timeout per run is 0h 00m 30s
> dup01.c:24: TPASS: dup(fd) returned fd 4
> dup01.c:27: TPASS: buf1.st_ino == buf2.st_ino (6921515)
> 
> Summary:
> passed   2
> failed   0
> broken   0
> skipped  0
> warnings 0
> 
> into:
> 
> $ LTP_REPRODUCIBLE_OUTPUT=1 ./testcases/kernel/syscalls/dup/dup01 
> tst_tmpdir.c:316: 
> tst_test.c:1907: 
> tst_test.c:1911: 
> tst_kconfig.c:88: 
> tst_test.c:1729: 
> dup01.c:24: 
> dup01.c:27: 
> 
> Summary:
> passed   2
> failed   0
> broken   0
> skipped  0
> warnings 0
> 
> So that still shows the "code flow" and the test results Summary (all
> output goes to stderr). I think this would indeed be useful to compare
> if a testcase runs the same "native" and under valgrind.

I will send a proper LTP patch.

-- 
Cyril Hrubis
chrubis@suse.cz