Control: tag -1 moreinfo On Sun, Nov 27, 2022 at 14:21:52 +0800, Eric Long wrote:
> Source: mercurial > Version: 6.2.3-1 > Severity: important > Tags: ftbfs patch > Justification: fails to build from source (but built successfully in the past) > User: debian-ri...@lists.debian.org > Usertags: riscv64 > X-Debbugs-Cc: i...@hack3r.moe, debian-ri...@lists.debian.org > > Dear maintainer(s), > > Some tests time out on riscv64 as seen in buildd log: > > ``` > Failed test-copies-chain-merge.t#pull: timed out > Failed test-copies-chain-merge.t#pull-upgrade: timed out > Failed test-copies-chain-merge.t#push: timed out > Failed test-copies-chain-merge.t#push-upgrade: timed out > Failed test-copies-chain-merge.t#sidedata: timed out > Failed test-copies-chain-merge.t#upgraded: timed out > Failed test-copies-chain-merge.t#upgraded-parallel: timed out > # Ran 892 tests, 80 skipped, 7 failed. > python hash seed: 74757585 > # Timout reached for process 2161206 > # Cleaning up HGTMP /tmp/hgtests.3yx9dxu8 > make[2]: *** [Makefile:140: tests] Error 1 > ``` > > Full log: > https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=riscv64&ver=6.2.3-1&stamp=1668895854&raw=0 > > These timeouts has existed for a long time (about a year), so maybe disable > them is a better idea for more consistent builds on riscv64. Alternatively, we > can increase test timeout further and hopefully let them finish in time. > > I've included a patch to disable those tests in debian/rules. Please let me > know if more help is needed. > I'd rather not duplicate the blacklist, that sounds like a maintenance nightmare. How long do these tests actually need on your hardware? Cheers, Julien
