Linux 5.12's very bad, double ungood day
Linux 5.12's very bad, double ungood day
Posted Mar 9, 2021 15:35 UTC (Tue) by pizza (subscriber, #46)In reply to: Linux 5.12's very bad, double ungood day by geert
Parent article: Linux 5.12's very bad, double ungood day
> That's why we linux-next, which is used for lots of automated integration tests
> Three weeks passed between the buggy commit entering linux-next and upstream.
> Three weeks passed between the buggy commit entering linux-next and upstream.
So the "problem" here isn't that nothing was being tested, it's just that none of the tests run during this interval window caught this particular issue. It's also not clear that there was even a test out there that could have caught this, except by pure happenstance.
But that's the reality of software work; a bug turns up, write a test to catch it (and hopefully others of the same class), add it to the test suite (which runs as often as your available resources allow) .... and repeat endlessly.