On Sun, Mar 3, 2024 at 10:39 AM Samuel Thibault <samuel.thiba...@gnu.org> wrote:
> Flávio Cruz, le jeu. 29 févr. 2024 22:01:41 -0500, a ecrit: > > On Thu, Feb 29, 2024 at 7:29 PM Samuel Thibault <[1] > samuel.thiba...@gnu.org> > > wrote: > > > > I could be wrong but if you look at this build log [3] > https://buildd.debian.org > > > /status/fetch.php?pkg=perl&arch=hurd-i386&ver=5.38.2-3&stamp=1705087520&raw=0 > > it fails on t/op/stat: > > > > > > t/op/stat ........................................................ # > Failed test 36 - ls and -b agreeing on /dev (0 310) at op/stat.t line 322 > > # got "0" > > # expected "310" > > # = before > > # total 1912 > > > > I did run the suite myself and it did seem to get stuck at listing /dev > when it > > attempted to open /dev/cd0. > > Oh? In my memory the issue I was seeing with op/stat was different. > Anyway, we will see, if it's solved then great :) > I just gave it a try with a patched system and indeed it doesn't seem to solve this problem. However, I also tested the vim testsuite and the existing hang VIMRUNTIME=../../runtime ../vim -f -u unix.vim --gui-dialog-file guidialog -U NONE --noplugin --not-a-term -S runtest.vim test_stat.vim --cmd 'au SwapExists * let v:swapchoice = "e"' | LC_ALL=C LANG=C LANGUAGE=C awk '/Executing Test_/{match($0, "([0-9][0-9]:[0-9][0-9] *)?Executing Test_[^\\)]*\\)"); print substr($0, RSTART, RLENGTH) "\r"; fflush()}' E: Build killed with signal TERM after 180 minutes of inactivity no longer happens. The test passes but the test suite goes on to fail on later tests. > Samuel >
