| Summary: | Update the LTP version in valgrind testsuite to 20250930 | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | mcermak |
| Component: | general | Assignee: | mcermak |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mark |
| Priority: | NOR | ||
| Version First Reported In: | 3.25 GIT | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | proposed patch | ||
|
Description
mcermak
2025-10-02 13:58:37 UTC
Created attachment 185475 [details] proposed patch This update seems to test fine. There are some new failures, but those relate to newly added testcases, which means these do not represent regressions. There are two exceptions: mknod06 and munmap01. These two tests are new and show something that looks like a regression at the first glance. But looking deeper, these were rewritten substantially. I suspect the change is related to the following one or two upstream commits: $ git log --pretty --oneline mknod06.c b3ddd9bad syscalls/mknod06: Convert to new API d34e76e75 lib/get_high_address.c: Add tst_get_bad_addr.h for new API [ ... ] $ Not easy to test because of some build problems these commits have. The other regression-like looking test results below are actually confirmed flukes: > $ diff old new > Only in new: clock_settime04.trs > Only in new: epoll_pwait06.trs > Only in new: file_attr01.trs > Only in new: file_attr02.trs > Only in new: file_attr03.trs > Only in new: file_attr04.trs > Only in new: ioctl10.trs > Only in new: ioctl_pidfd01.trs > Only in new: ioctl_pidfd02.trs > Only in new: ioctl_pidfd03.trs > Only in new: ioctl_pidfd04.trs > Only in new: ioctl_pidfd05.trs > Only in new: ioctl_pidfd06.trs > Only in old: kill07.trs > diff old/kill12.trs new/kill12.trs > 1c1 > < :test-result: FAIL > --- > > :test-result: PASS > Only in new: landlock09.trs > Only in new: landlock10.trs > Only in old: lchown03_16.trs > Only in old: lchown03.trs > Only in new: listxattr04.trs > Only in new: lsm_get_self_attr01.trs > Only in new: lsm_get_self_attr02.trs > Only in new: lsm_get_self_attr03.trs > Only in new: lsm_list_modules01.trs > Only in new: lsm_list_modules02.trs > Only in new: lsm_set_self_attr01.trs > diff old/mknod06.trs new/mknod06.trs > 1c1 > < :test-result: PASS > --- > > :test-result: FAIL > Only in new: mount08.trs > Only in new: mount_setattr02.trs > diff old/munmap01.trs new/munmap01.trs > 1c1 > < :test-result: PASS > --- > > :test-result: FAIL > Only in old: munmap02.trs > Only in new: munmap04.trs > diff old/pipe13.trs new/pipe13.trs > 1c1 > < :test-result: PASS > --- > > :test-result: FAIL > diff old/set_thread_area01.trs new/set_thread_area01.trs > 1c1 > < :test-result: FAIL > --- > > :test-result: PASS > Only in new: set_thread_area02.trs > Only in new: statmount09.trs > Only in new: unshare05.trs > $ That said, seems like this LTP update patch is good to go. (In reply to mcermak from comment #1) > Created attachment 185475 [details] > proposed patch > > seems like this LTP update patch is good to go. Agreed, looks good. Please apply. Commit a04974ddcb51fbb24b1e44b1f9c98d0a11356cca . |