Hi Randall, I don't have access to a HPE NonStop system to test but I think I've found the two issues you hit. Both only impact the testsuite not the built rsync binary. I've opened a PR to fix it here: https://github.com/RsyncProject/rsync/pull/902 I'd appreciate it if you could test it. Cheers, Tridge
On Thu, 21 May 2026 at 02:03, <[email protected]> wrote: > > Please be aware that we are having new issues with 3.4.3 in the following > tests. This is likely a problem with capability on the HPE NonStop platform > as used in your test structure with multi-layer test -h > > > > ----- chmod-symlink-race log follows > > Testing for symlinks using 'test -h' > > [tester] exceeded --max-alloc=0 setting (file=syscall.c, line=1857) > > exit(22): /home/jenkinsbuild/.jenkins/workspace/Rsync_Pipeline/util2.c(80) > > t_chmod_secure reported failures (see stderr above) > > ----- chmod-symlink-race log ends > > > > ----- symlink-dirlink-basis log follows > > Testing for symlinks using 'test -h' > > failed to create test file > /home/jenkinsbuild/.jenkins/workspace/Rsync_Pipeline/testtmp/symlink-dirlink-basis/src/dir/file > > ----- symlink-dirlink-basis log ends > > FAIL symlink-dirlink-basis > > Any advice on dealing with this? > > > > Thanks, > > Randall -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
