On Sep 30, 7:40pm, Axel Beckert wrote:
}
} But I have a slight hope that enabling verbose output avoids some race
} condition which is triggering this issue occasionally.
That's quite likely.
Also the patch in zsh-workers/33298 may resolve some deadlocks caused by
signals interrupting memory
Hi Bart,
Bart Schaefer wrote:
On Sep 30, 7:40pm, Axel Beckert wrote:
} But I have a slight hope that enabling verbose output avoids some race
} condition which is triggering this issue occasionally.
That's quite likely.
Perfect. :-)
Also the patch in zsh-workers/33298 may resolve some
Hi again,
Axel Beckert wrote:
And this time I had some luck after something like 70 to 100
successful package builds in one row, […]
It actually were 118 successful builds in a row before the first test
suite run was hanging.
Axel Beckert wrote:
Bart Schaefer wrote:
Again this could be in
On Sep 29, 3:51am, Axel Beckert wrote:
}
} 1) Hangs in the static build at
}
} ../../Test/A04redirect.ztst: starting.
This doesn't mean very much; none of the tests in A04 produce any output
(unless they fail) so it could be stuck anywhere.
To refine, the make check need to be run with
Hi again,
Axel Beckert wrote:
This means the issue occurred while running the test suite against the
static build of the test suite.
I'll tomorrow check the other failed builds if that was the case
there, too.
I was too curious, so I checked all buildd logs with hanging test
suites
5 matches
Mail list logo
