Package: mercurial Version: 5.4.1-1 Followup-For: Bug #956697 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy ubuntu-patch
Dear Maintainer, In Ubuntu's autopkgtest infrastructure I also noticed that the test-wireproto-exchangev2-shallow.t is flaky as the ordering of the output changes. Its worth mentioning that the test fails more frequently on armhf. Here are some logs of it failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/m/mercurial/20200630_044520_38521@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/m/mercurial/20200523_005337_84d39@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/m/mercurial/20200524_200914_c544f@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/m/mercurial/20200524_200914_c544f@/log.gz In Ubuntu, the attached patch was applied to achieve the following: * Blacklist for test-wireproto-exchangev2-shallow.t for occasional failures. Thanks for considering the patch.
diff -Nru mercurial-5.4.1/debian/mercurial.test_blacklist mercurial-5.4.1/debian/mercurial.test_blacklist --- mercurial-5.4.1/debian/mercurial.test_blacklist 2020-06-25 08:48:40.000000000 -0700 +++ mercurial-5.4.1/debian/mercurial.test_blacklist 2020-07-01 11:12:41.000000000 -0700 @@ -37,3 +37,4 @@ test-commandserver.t test-largefiles.t test-wireproto-exchangev2.t +test-wireproto-exchangev2-shallow.t
