On Thu, Feb 27, 2025 at 01:14:12PM -0600, Eric Blake wrote:
> On Tue, Feb 25, 2025 at 08:06:50AM +0100, Thomas Huth wrote:
> > Test 162 recently started failing for me for no obvious reasons (I
> > did not spot any suspicious commits in this area), but looking in
> > the 162.out.bad log file, there
On Tue, Feb 25, 2025 at 08:06:50AM +0100, Thomas Huth wrote:
> Test 162 recently started failing for me for no obvious reasons (I
> did not spot any suspicious commits in this area), but looking in
> the 162.out.bad log file, there was a suspicious message at the end:
>
> qemu-nbd: Cannot lock pi
On 25/02/2025 08.06, Thomas Huth wrote:
Test 162 recently started failing for me for no obvious reasons (I
did not spot any suspicious commits in this area), but looking in
the 162.out.bad log file, there was a suspicious message at the end:
qemu-nbd: Cannot lock pid file: Resource temporarily
Test 162 recently started failing for me for no obvious reasons (I
did not spot any suspicious commits in this area), but looking in
the 162.out.bad log file, there was a suspicious message at the end:
qemu-nbd: Cannot lock pid file: Resource temporarily unavailable
And indeed, the test starts t
