On Fri, Aug 12, 2022 at 03:02:36PM +0200, Paul Gevers wrote: > On 12-08-2022 12:23, Marc Haber wrote: > > On Thu, Aug 11, 2022 at 10:51:32PM +0200, Paul Gevers wrote: > > > On 10-08-2022 12:03, Marc Haber wrote: > > > > I tried the (dead simple)d autopkgtest on the s390s and arm64 > > > > porterboxes > > > > and it succeeded in a second's time. I have sharpened the expression > > > > that counts the CPUs in lscpu's output and hope this will fix the issue. > > > > > > ooo, CPU count. Yes, some of those archs run on hosts with lots of CPU's. > > > armhf has 160, s390x has 10. > > > > I am testing locally on amd64 with a machine with 12 CPUs. The armhf > > tests succeed (see > > https://ci.debian.net/data/autopkgtest/testing/armhf/a/atop/24578667/log.gz). > > Great, same on arm64. s390x still times out though.
And I would love to know which of the two pipes hang. On zelenka, everything is just fine. > > The complete test is: > > #!/bin/bash > > > > # atop reports number of CPU and two extra lines > > ATOPSOPINION="$(atop -P cpu 5 1 | grep -vE '^(RESET|SEP)' | wc -l)" > > When I run `atop` manually (on stable), it doesn't do anything... > root@ci-worker-s390x-01:~# atop > ^C > > I started up a clean unstable lxc container and installing atop takes quite > some time between: > Created symlink /etc/systemd/system/timers.target.wants/atop-rotate.timer -> > /lib/systemd/system/atop-rotate.timer. > Created symlink /etc/systemd/system/multi-user.target.wants/atop.service -> > /lib/systemd/system/atop.service. > Created symlink /etc/systemd/system/multi-user.target.wants/atopacct.service > -> /lib/systemd/system/atopacct.service. > and > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. > > running atop from unstable also hangs: > root@elbrus:~# atop > ^C on zelenka, running the atop binary just works fine. Installing atop 2.7.1-2 in a DD chroot on zelenka also works fine, and the binary is ok as well. However, the chroots dont start the services though. > > There is no loop, and nothing that could fail on a big number. In my > > understanding, this could run on a box with 2000 cores and still work. > > Except, it doesn't. Seems like atop is seriously broken on s390x on the > hosts that we have. Except zelenka, the only machine that is easily accessible to me. Everything is just fine there. > > Also, the test does not time out on zelenka when manually invoked in an > > schroot (setting PATH to point to an executable atop is necessary, as it > > does not seem to be possible to install an abitrary package that is not > > in the archive. Also, the test is successful if invoked after installing > > atop 2.7.1-2 from the archive. > > Maybe we need to involve the s390x porters? I put them in CC to already draw > their attention. That's what I did yesterday. Their mailing list seems to be a cozy quiet place though. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
