Could you try removing ayatana-indicator-session from the ci.debian.net reject list? The autopkgtest is working now in Salsa CI and in Ubuntu's infrastructure. https://salsa.debian.org/debian-ayatana-team/ayatana-indicator-session/-/pipelines https://autopkgtest.ubuntu.com/packages/ayatana-indicator-session Thank you, Jeremy Bícha
Hi, I scheduled one run on each architecture on testing. It failed on each one: bash: line 1: obj-*/tests/test-service: No such file or directory "Internal Server Error" so I can't check. My comment in the reject_list is this: "test suite interacts badly sometimes with infrastructure". So I wonder how to monitor this as I have no clue anymore what the indications were of "interacts badly". I worry about the "sometimes" part. My git commit message said: "ayatana-indicator-session sometimes 'hangs' the debci worker for 28h and otherwise always fails" If you fix the test, I'll unblock and try to monitor for a while. Paul
I probably should have waited a few days before requesting this. I fixed the obj-* issue in ayatana-indicator-session 26.6.1-2 but it hasn't migrated to Testing yet. Thank you, Jeremy Bícha
Hi I should have checked unstable before sending. I ran the tests in unstable too and there they pass everywhere. Still applies. So, I'll unblock now. Paul
Hi,
And it already seems that one of my scheduled tests is hanging. Do you
spot here what goes wrong?
root@ci-196-5c63f04a:/# ps faux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1039 0.0 0.0 7776 4224 pts/5 Ss 17:37 0:00 /bin/bash
root 1042 0.0 0.0 9552 3968 pts/5 R+ 17:38 0:00 \_
ps faux
root 720 0.0 0.0 7488 3744 ? S 17:04 0:00 bash
-c set -a; [ -r /etc/environment ] && . /etc/environment 2>/dev/nul
root 723 0.0 0.0 2688 1712 ? S 17:04 0:00 \_
/bin/sh -ec "$@" 3>&2 2>&1 run_apt_command /usr/bin/eatmydata apt-ge
root 724 0.0 0.0 100672 87200 ? S 17:04 0:01
\_ /usr/bin/apt-get --quiet --assume-yes -o=APT::Status-Fd=3 -o=APT
_apt 733 0.2 0.0 23648 12176 ? S 17:04 0:04
\_ /usr/lib/apt/methods/http
root 1 0.0 0.0 18992 13056 ? Ss 17:04 0:00
/sbin/init
root 39 0.0 0.0 27440 10720 ? Ss 17:04 0:00 \_
/usr/lib/systemd/systemd-journald
message+ 77 0.0 0.0 8784 4128 ? Ss 17:04 0:00 \_
/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfil
_dhcpcd 79 0.0 0.0 10016 4560 ? Ss 17:04 0:00 \_
dhcpcd: eth0 [ip4] [ip6]
root 80 0.0 0.0 9840 2592 ? S 17:04 0:00 |
\_ dhcpcd: [privileged proxy] eth0 [ip4] [ip6]
_dhcpcd 109 0.0 0.0 9840 2448 ? S 17:04 0:00 |
| \_ dhcpcd: [DHCP6 proxy] fe80::1266:6aff:fe9f:653a
_dhcpcd 128 0.0 0.0 9840 2448 ? S 17:04 0:00 |
| \_ dhcpcd: [DHCP6 proxy] fc42:5009:ba4b:5ab0:2e6c:b528:8d08:7a5
_dhcpcd 339 0.0 0.0 9840 2384 ? S 17:04 0:00 |
| \_ dhcpcd: [BPF ARP] eth0 10.0.40.7
_dhcpcd 373 0.0 0.0 9840 2320 ? S 17:04 0:00 |
| \_ dhcpcd: [BOOTP proxy] 10.0.40.7
_dhcpcd 81 0.0 0.0 9808 2256 ? S 17:04 0:00 |
\_ dhcpcd: [network proxy] eth0 [ip4] [ip6]
_dhcpcd 82 0.0 0.0 9808 2192 ? S 17:04 0:00 |
\_ dhcpcd: [control proxy] eth0 [ip4] [ip6]
root 83 0.0 0.0 11312 6576 ? Ss 17:04 0:00 \_
/usr/lib/systemd/systemd-logind
root 146 0.0 0.0 7824 2624 pts/0 Ss+ 17:04 0:00 \_
/usr/sbin/agetty --noreset --noclear --keep-baud 115200,57600,38400,
root 147 0.0 0.0 11264 7728 ? Ss 17:04 0:00 \_
sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
Hi, Last time for now. This was just the default loong64 host location problem: it was taking a long time to install all required binaries as a lot weren't in the cache yet. Paul
I think we can close this bug now? https://ci.debian.net/packages/a/ayatana-indicator-session/ Thank you, Jeremy Bícha
Hi Jeremy, Thanks for the ping, it dropped from my radar. Closing now. Paul