Hi all, I would like to raise awareness of a series of unreasonable riscv64 autopkgtest failures, as shown on https://ci.debian.net/packages/libw/libwww-telegram-botapi-perl/testing/riscv64/ after 2024-09-13. As an example, https://ci.debian.net/data/autopkgtest/testing/riscv64/libw/libwww-telegram-botapi-perl/51638312/log.gz shows that the autopkgtest machines tries to use debug-debug repository from https://mirrors.tuna.tsinghua.edu.cn/debian-debug , which does not exist from the very beginning [2]. It causes the autopkgtest to fail. =========================================== 0s autopkgtest [01:36:10]: starting date and time: 2024-09-14 01:36:10+0000 0s autopkgtest [01:36:10]: version 5.39 0s autopkgtest [01:36:10]: host debci-16; command line: /usr/bin/autopkgtest --no-built-binaries '--setup-commands=echo '"'"'libwww-telegram-botapi-perl testing/riscv64'"'"' > /var/tmp/debci.pkg 2>&1 || true' '--setup-commands=echo '"'"'Acquire::Retries "10";'"'"' > /etc/apt/apt.conf.d/75retry 2>&1 || true' --timeout=30600 --timeout-factor=2 -- user debci --apt-upgrade --pin-packages=unstable=src:libwww-telegram-botapi-perl '--add-apt-source=deb-src http://deb.debian.org/debian unstable main contrib non-free non- free-firmware 0s deb http://deb.debian.org/debian unstable main contrib non-free non-free-firmware' --output-dir /tmp/debci-worker-51638312-SamZZCyd7y/autopkgtest- incoming/testing/riscv64/libw/libwww-telegram-botapi-perl/51638312 libwww-telegram-botapi-perl -- lxc --sudo --name ci-258-f345c4ff autopkgtest-testing-riscv64 32s autopkgtest [01:36:42]: testbed dpkg architecture: riscv64 32s autopkgtest [01:36:42]: testbed apt version: 2.9.8 32s autopkgtest [01:36:42]: @@@@@@@@@@@@@@@@@@@@ test bed setup 35s Get:1 http://deb.debian.org/debian unstable InRelease [198 kB] 37s Get:2 http://deb.debian.org/debian unstable/main Sources [10.8 MB] 39s Get:3 http://deb.debian.org/debian unstable/non-free Sources [84.9 kB] 39s Get:4 http://deb.debian.org/debian unstable/contrib Sources [61.8 kB] 39s Get:5 http://deb.debian.org/debian unstable/non-free-firmware Sources [7,076 B] 39s Get:6 http://deb.debian.org/debian unstable/main riscv64 Packages [9,557 kB] 40s Get:7 http://deb.debian.org/debian unstable/non-free-firmware riscv64 Packages [6,336 B] 40s Get:8 http://deb.debian.org/debian unstable/contrib riscv64 Packages [46.6 kB] 40s Get:9 http://deb.debian.org/debian unstable/non-free riscv64 Packages [57.0 kB] 52s Fetched 20.8 MB in 19s (1,077 kB/s) 59s Reading package lists... 62s Get:1 https://mirrors.tuna.tsinghua.edu.cn/debian testing InRelease [169 kB] 62s Ign:2 https://mirrors.tuna.tsinghua.edu.cn/debian-debug testing-debug InRelease 62s Err:3 https://mirrors.tuna.tsinghua.edu.cn/debian-debug testing-debug Release 62s 404 Not Found [IP: 101.6.15.130 443] 62s Hit:4 http://deb.debian.org/debian unstable InRelease 79s Get:5 https://mirrors.tuna.tsinghua.edu.cn/debian testing/non-free-firmware Sources [6,940 B] 79s Get:6 https://mirrors.tuna.tsinghua.edu.cn/debian testing/main Sources [10.1 MB] 81s Get:7 https://mirrors.tuna.tsinghua.edu.cn/debian testing/non-free Sources [74.1 kB] 81s Get:8 https://mirrors.tuna.tsinghua.edu.cn/debian testing/contrib Sources [47.7 kB] 81s Get:9 https://mirrors.tuna.tsinghua.edu.cn/debian testing/contrib riscv64 Packages [34.4 kB] 81s Get:10 https://mirrors.tuna.tsinghua.edu.cn/debian testing/non-free-firmware riscv64 Packages [6,336 B] 81s Get:11 https://mirrors.tuna.tsinghua.edu.cn/debian testing/main riscv64 Packages [7,893 kB] 82s Get:12 https://mirrors.tuna.tsinghua.edu.cn/debian testing/non-free riscv64 Packages [53.7 kB] 101s Reading package lists... 101s E: The repository 'https://mirrors.tuna.tsinghua.edu.cn/debian-debug testing-debug Release' does not have a Release file. 101s blame: 101s badpkg: testbed setup commands failed with status 100 101s autopkgtest [01:37:51]: ERROR: erroneous package: testbed setup commands failed with status 100 ============================================ I have no idea why the autopkgtest machine would look for this repository on mirrors.tuna.tsinghua.edu.cn. Is that some kind of manual config? If yes, such configuration needs to be corrected as soon as possible. Thanks, Boyuan Yang [2] https://github.com/tuna/issues/issues/644
Attachment:
signature.asc
Description: This is a digitally signed message part