NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-pmax/54923 (pmax test runs fail to complete since Jan 15)
The following reply was made to PR port-pmax/54923; it has been noted by GNATS.
From: Andreas Gustafsson <gson%gson.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc:
Subject: Re: port-pmax/54923 (pmax test runs fail to complete since Jan 15)
Date: Sat, 15 Feb 2020 13:30:30 +0200
On Feb 5, I wrote:
> FWIW, the last three test runs have completed, but I'm having a hard
> time figuring out which commit could have fixed it. The first
> completed run is:
>
> http://releng.netbsd.org/b5reports/pmax/commits-2020.02.html#2020.02.02.09.19.48
>
> I have started a few more builds to narrow it down.
After many additional test runs, I'm still confused as to what is
going on. My own testbed agress with the TNF one that the problem
started with ad's commits of Jan 15:
http://releng.netbsd.org/b5reports/pmax/commits-2020.01.html#2020.01.15.17.55.43
http://www.gson.org/netbsd/bugs/build/pmax/commits-2020.01.html#2020.01.15.17.55.43
On both testbeds, the tests then consistently failed to complete until
around Feb 2, but since then, the behavior has been random and
different between the testbeds:
http://releng.netbsd.org/b5reports/pmax/commits-2020.02.html#2020.02.02.06.41.27
http://www.gson.org/netbsd/bugs/build/pmax/commits-2020.02.html#2020.02.02.03.41.12
The pmax tests have been printing the message "warning: LOW reference"
since ~forever, but what has changed is that they now end up printing
them in a tight loop (or not, as the case may be).
The hpcmips tests have failed to complete in every run since Jan 15,
but it's hard to tell if the problem started with the same commit as
the pmax one because they were already randomly failing to complete
before that:
http://releng.netbsd.org/b5reports/hpcmips/commits-2020.01.html#2020.01.15.15.30.46
--
Andreas Gustafsson, gson%gson.org@localhost
Home |
Main Index |
Thread Index |
Old Index