Source: piuparts Version: 1.6.0 Severity: important User: debian...@lists.debian.org Usertags: flaky X-Debbugs-Cc: elb...@debian.org
Dear Maintainer, piuparts's tests fail very often (but not always) on riscv64: https://ci.debian.net/packages/p/piuparts/unstable/riscv64/ and always fail on loong64: https://ci.debian.net/packages/p/piuparts/unstable/loong64/ But unfortunately, I haven't found the root cause of theis problem until now. From these logs, these test cases failed like: ``` 781s Get:1 http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease [208 kB] 781s Err:1 http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease 781s Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Message has been manipulated Verifying signature: Message has been manipulated 781s Reading package lists... 781s W: OpenPGP signature verification failed: http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Message has been manipulated Verifying signature: Message has been manipulated 781s E: The repository 'http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease' is not signed. 781s 2m8.7s ERROR: Command failed (status=100): ['chroot', '/tmp/tmpmxrgp2jc', 'eatmydata', 'apt-get', 'update'] 781s Get:1 http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease [208 kB] 781s Err:1 http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease 781s Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Message has been manipulated Verifying signature: Message has been manipulated 781s Reading package lists... 781s W: OpenPGP signature verification failed: http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Message has been manipulated Verifying signature: Message has been manipulated 781s E: The repository 'http://mirrors.tuna.tsinghua.edu.cn/debian sid InRelease' is not signed. ``` https://ci.debian.net/packages/p/piuparts/unstable/riscv64/60668778/#L1180 But this is impossible, we rely heavily on this mirror every day. But on these logs failed, we can find the warnings on riscv64: ``` 17s auto-apt-proxy: INFO: looking for available APT cache 18s auto-apt-proxy: INFO: no proxy detected 18s auto-apt-proxy: INFO: using cache: no proxy detected (ttl = 59s) 18s Get:1 http://mirrors.tuna.tsinghua.edu.cn/debian unstable InRelease [205 kB] 19s auto-apt-proxy: INFO: using cache: no proxy detected (ttl = 58s) 19s Get:2 http://mirrors.tuna.tsinghua.edu.cn/debian unstable/main Sources.diff/Index [63.6 kB] 19s auto-apt-proxy: INFO: using cache: no proxy detected (ttl = 58s) 21s Get:3 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB] 21s Get:4 http://mirrors.tuna.tsinghua.edu.cn/debian unstable/main riscv64 Packages.diff/Index [63.6 kB] 21s auto-apt-proxy: INFO: using cache: no proxy detected (ttl = 56s) 23s auto-apt-proxy: INFO: using cache: no proxy detected (ttl = 54s) ``` So I suspect the failure has something to do with this. Another proof is that I can pass the autopkgtest on my local risv64 hardware(Unmatched) without apt-proxy. I just put my thoughts on here and I will debug it when I have enough time. -- Regards, -- Bo YU
signature.asc
Description: PGP signature
