LWN: Comments on "Kernel test automation with LTP" https://lwn.net/Articles/625969/ This is a special feed containing comments posted to the individual LWN article titled "Kernel test automation with LTP". en-us Fri, 03 Oct 2025 23:55:57 +0000 Fri, 03 Oct 2025 23:55:57 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Kernel test automation with LTP https://lwn.net/Articles/627194/ https://lwn.net/Articles/627194/ metan It can run automatic tests as well, among others it can run subset of LTP as of now (mostly syscall tests). Have a look at the <a rel="nofollow" href="https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/tree/jobs">LKP jobs definitions</a> Sun, 21 Dec 2014 10:11:52 +0000 Kernel test automation with LTP https://lwn.net/Articles/627158/ https://lwn.net/Articles/627158/ ploxiln <div class="FormattedComment"> That just tests "does the kernel build and boot successfully" for a few configurations, IIRC. It needs to be fast because it tests many commits appearing in various git trees.<br> </div> Sat, 20 Dec 2014 19:53:42 +0000 Kernel test automation with LTP https://lwn.net/Articles/627024/ https://lwn.net/Articles/627024/ jezuch <div class="FormattedComment"> I've read a lot about "Fengguang Wu's testing infrastructure" here and elsewhere. How does that relate to LTP?<br> </div> Fri, 19 Dec 2014 12:54:56 +0000 Kernel test automation with LTP https://lwn.net/Articles/626837/ https://lwn.net/Articles/626837/ flussence <div class="FormattedComment"> I wish I'd known about the existence of that `getconf` command! I've been doing it wrong this whole time by parsing the output of lscpu.<br> </div> Thu, 18 Dec 2014 17:17:24 +0000 Kernel test automation with LTP https://lwn.net/Articles/626743/ https://lwn.net/Articles/626743/ xz <div class="FormattedComment"> People have not been running LTP enough. Remember the leap second of doom bug in 2012? <a href="http://lwn.net/Articles/504744/">http://lwn.net/Articles/504744/</a> <a href="http://lwn.net/Articles/509207/">http://lwn.net/Articles/509207/</a><br> <p> It turned out this bug was entirely avoidable if LTP was run beforehand and the results were analyzed for the leap second situation. After the bug happened, I ran LTP with leap second transition, and immediately multiple time and lock related POSIX tests failed or caused kernel hang. That meant nobody had ever run LTP for the leap second situation or had not seriously looked at the results if they did.<br> </div> Thu, 18 Dec 2014 07:51:03 +0000