Re: Question regarding the "Top 10 Oldest Problem Reports" in GNATS

[smurfd <smurf.daemon%mail.smurfd.me@localhost>]

On 6/15/26 4:51 PM, Greg Troxel wrote:
> Aryabhata <bsdhexa%gmail.com@localhost> writes:
>
> > I was recently looking through the GNATS summary page (
> > https://gnats.netbsd.org/summary/) and noticed the "Top 10 Oldest Problem
> > Reports" list.
> >
> > Most of these PRs date back to before the year 2000. Given how much the
> > system, hardware landscapes, and codebase have evolved over the last two
> > and a half decades, I wanted to ask the developer community whether it
> > makes sense to keep these open, or if it would be better to close them out.
> >
> > Are these ancient reports still tracked for historical/architectural
> > relevance, or could they safely be closed to help clean up the tracker? If
> > some are still valid, it might be worth verifying if they are still
> > reproducible on modern NetBSD releases.
> You are welcome to dig in and help, and read them and assess relevance
> and test.  It sounds like you are suggesting that Some Else(tm) to that.

Hey

Sorry if this is not the way to do this, but this one: https://gnats.netbsd.org/2107
Seems to have been resolved:
$ sa -m
root       2130988       201.82cpu            0tio    34902601k*sec (while trying to build netbsd)
user            62         0.10cpu            0tio           9k*sec

A guess is that the problem was introduced here:
https://github.com/NetBSD/src/commit/a62207fee87968db553efb0215be21c6b1722f61

And resolved here:
https://github.com/NetBSD/src/commit/c2aa46e7c277e040ee9dd4f36ac7434a63d2c8e4

Br