I got a test-clone-uncompressed.t failure: --- /<<PKGBUILDDIR>>/tests/test-clone-uncompressed.t +++ /<<PKGBUILDDIR>>/tests/test-clone-uncompressed.t#stream-bundle2.err @@ -404,6 +404,8 @@ $ echo >> repo/f1 $ echo >> repo/f2 $ hg -R repo ci -m "1" + waiting for lock on repository repo held by process '31769' on host 'mipsel-aql-01/effffffc' + got lock after 1 seconds $ wait $ hg -R clone id 000000000000 I guess that's what the "sleep 1" in there is meant to avoid, but it's not too reliable. Full log: https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=mipsel&ver=5.2.1-1&stamp=1575682754&raw=0
Bug was set to UNCONFIRMED for 31 days, bumping
Bug was set to UNCONFIRMED for 30 days, bumping
The logs shows it
https://phab.mercurial-scm.org/D8664
Fixed by https://mercurial-scm.org/repo/hg/rev/752da6863e39 Julien Cristau <jcristau@debian.org> test: redirect stderr so warning messages don't change output (issue6237) clone and commit race for the lock, and if commit has to wait more than a second it prints a warning to stderr. Since this is somewhat expected here, silence it. Differential Revision: https://phab.mercurial-scm.org/D8664 (please test the fix)
Bug was set to TESTING for 7 days, resolving
Fixed by https://mercurial-scm.org/repo/hg/rev/23119371df5e Pierre-Yves David <pierre-yves.david@octobus.net> test-clone-uncompressed: use config to silence the lock warning The ui.timeout.warn option can solve the issue6237 in a cleaner way than what was done in 752da6863e39. That way, possible other unexpected error output will not be silenced. Differential Revision: https://phab.mercurial-scm.org/D8726 (please test the fix)