8 ms·

It is insane to me that kernel maintainers do not have build pipelines that automatically run for every PR. The computers should be checking formatting, basic c

It is insane to me that kernel maintainers do not have build pipelines that automatically run for every PR. The computers should be checking formatting, basic compilation, testing, etc etc.

Ericson2314 5y ago
At the very least, before I opened the floodgates to github-style contributions, I would want to already have damn good CI in place. While I firmly believe in "trickle up" economics", I still believe in trickle down productivity investment. It is important to increase the productivity of patch review (CI, etc., done by the experts manually today) before increasing the productivity of patch submission (done by everyone else).
MuffinFlavored 5y ago
I'd love to hear from Linus why they don't have that. I know it's probably super hard to "unit test" some of this stuff but... does the Linux kernel have effectively 0 testing?
- viraptor 5y ago
  No, they have various testing platforms and harnesses, but they're very component oriented. For example people doing filesystem development will use https://github.com/kdave/xfstests https://github.com/kdave/xfstests for validation. Others will use different tools. At Linux kernel level you can't effectively have "a CI". Unless you have massive amounts of funds and time to invest of course. I'm sure MS has some complex pre-release automation.
ploxiln 5y ago
They actually do, it's just somewhat distributed. https://01.org/lkp/documentation/0-day-test-service https://01.org/lkp/documentation/0-day-test-service https://linux.kernelci.org/job/ https://linux.kernelci.org/job/ "kernel test robot" example email: https://lore.kernel.org/netdev/202102070253.xooT3PWR-lkp@intel.com/ https://lore.kernel.org/netdev/202102070253.xooT3PWR-lkp@int...
castratikron 5y ago
I submitted some changes a couple years ago and something named "Hulk Robot" at Huawei found my change didn't build with a certain kernel config, and sent a patch to fix. I think there's a lot of distributed checking going on even if kernel.org doesn't have an official pipeline or unit testing.

It is insane to me that kernel maintainers do not have build pipelines that automatically run for every PR. The computers should be checking formatting, basic compilation, testing, etc etc.

Ericson2314 5y ago

At the very least, before I opened the floodgates to github-style contributions, I would want to already have damn good CI in place. While I firmly believe in "trickle up" economics", I still believe in trickle down productivity investment. It is important to increase the productivity of patch review (CI, etc., done by the experts manually today) before increasing the productivity of patch submission (done by everyone else).

MuffinFlavored 5y ago

I'd love to hear from Linus why they don't have that. I know it's probably super hard to "unit test" some of this stuff but... does the Linux kernel have effectively 0 testing?

viraptor 5y ago
No, they have various testing platforms and harnesses, but they're very component oriented. For example people doing filesystem development will use https://github.com/kdave/xfstests https://github.com/kdave/xfstests for validation. Others will use different tools. At Linux kernel level you can't effectively have "a CI". Unless you have massive amounts of funds and time to invest of course. I'm sure MS has some complex pre-release automation.

ploxiln 5y ago

They actually do, it's just somewhat distributed. https://01.org/lkp/documentation/0-day-test-service https://01.org/lkp/documentation/0-day-test-service https://linux.kernelci.org/job/ https://linux.kernelci.org/job/ "kernel test robot" example email: https://lore.kernel.org/netdev/202102070253.xooT3PWR-lkp@intel.com/ https://lore.kernel.org/netdev/202102070253.xooT3PWR-lkp@int...

castratikron 5y ago

I submitted some changes a couple years ago and something named "Hulk Robot" at Huawei found my change didn't build with a certain kernel config, and sent a patch to fix. I think there's a lot of distributed checking going on even if kernel.org doesn't have an official pipeline or unit testing.