Re: Testbed breakage

2019-12-06 Thread Andrew Doran
Hi,

On Fri, Dec 06, 2019 at 04:03:05PM +0200, Andreas Gustafsson wrote:

> For the last few days, most of the testbeds have been seeing the
> system under test either hang or panic before the ATF tests have run
> to completion.  The failures are too many and varied to file a PR
> about each, but for a start, you can look for "tests: did not
> complete" in the following:
> 
>   http://releng.netbsd.org/b5reports/i386/commits-2019.12.html
>   http://releng.netbsd.org/b5reports/amd64/commits-2019.12.html
>   http://releng.netbsd.org/b5reports/evbarm-aarch64/commits-2019.12.html
>   http://releng.netbsd.org/b5reports/pmax/commits-2019.12.html
> 
> For sparc, there is PR 54734.  Both qemu and gxemul based testbeds are
> failing, but my i386 and amd64 testbeds running on real hardware are
> not (other than the latest amd64 test run showing 1336 new test
> failures, which looks like an unrelated bug).  That the failing hosts
> are uniprocessors and the working ones are multiprocessors may or may
> not be a coincidence.

I think may have just fixed the hangs:

http://mail-index.netbsd.org/source-changes/2019/12/06/msg111617.html

The xcall related crash is baffling.  I will spend a little time to look
into it over the weekend.

Andrew


Testbed breakage

2019-12-06 Thread Andreas Gustafsson
Hi all,

For the last few days, most of the testbeds have been seeing the
system under test either hang or panic before the ATF tests have run
to completion.  The failures are too many and varied to file a PR
about each, but for a start, you can look for "tests: did not
complete" in the following:

  http://releng.netbsd.org/b5reports/i386/commits-2019.12.html
  http://releng.netbsd.org/b5reports/amd64/commits-2019.12.html
  http://releng.netbsd.org/b5reports/evbarm-aarch64/commits-2019.12.html
  http://releng.netbsd.org/b5reports/pmax/commits-2019.12.html

For sparc, there is PR 54734.  Both qemu and gxemul based testbeds are
failing, but my i386 and amd64 testbeds running on real hardware are
not (other than the latest amd64 test run showing 1336 new test
failures, which looks like an unrelated bug).  That the failing hosts
are uniprocessors and the working ones are multiprocessors may or may
not be a coincidence.

Please help find and fix the offending commit(s); until that is done,
there can be very little automated testing of new commits.
-- 
Andreas Gustafsson, g...@gson.org