From patchwork Thu Mar 26 14:35:04 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [Bug,6294] New: test-debugcommands.t unreliability
From: mercurial-bugs@mercurial-scm.org
X-Patchwork-Id: 45915
Message-Id:
To: mercurial-devel@mercurial-scm.org
Date: Thu, 26 Mar 2020 14:35:04 +0000
https://bz.mercurial-scm.org/show_bug.cgi?id=6294
Bug ID: 6294
Summary: test-debugcommands.t unreliability
Product: Mercurial
Version: stable branch
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzilla@mercurial-scm.org
Reporter: jcristau@debian.org
CC: mercurial-devel@mercurial-scm.org
Python Version: ---
I got a failure in that test running on armel and python3.8:
https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=armel&ver=5.3.1-1%2Bexp1&stamp=1585159304&raw=0
ERROR: test-debugcommands.t output changed
A previous run didn't fail, so I guess it's a race condition.
--- /<>/tests/test-debugcommands.t
+++ /<>/tests/test-debugcommands.t.err
@@ -517,10 +517,11 @@
$ hg debuglocks
lock: free
- wlock: user *, process * (*s) (glob)
- [1]
+ wlock: free
$ hg debuglocks -W
+ abort: $ENOENT$: '$TESTTMP/debugrevlog/.hg/wlock'
+ [255]
$ hg debuglocks
lock: free