Getting started now in Floriana II. :) #LinuxPlumberspic.twitter.com/7YZgvtOZxS
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
The CKI team is pronounced "cookie" and there are cookies in the back of the room (if you're here in the room).
Developers and QE kicking kernels over the wall lead to pain. Bugs eventually make their way downstream and are difficult to fix that late in the process.
Automatic kernel tests run against kernel trees inside Red Hat (with every proposed contribution). It's better to run the tests earlier and more often to find the bugs sooner and faster. This hopefully leads to fewer bugs in the kernel (Red Hat's kernel and upstream).
Testing runs across five architectures and tons of different platforms (laptops, servers, mainframes) with lots of different hardware. Tests come from upstream and internal sources. Lots of internal tests are going upstream!
Every test results in a detailed report email that explains what tests failed. Logs, built artifacts, and kernel configs are all available for fast download.
The CKI team uses very recent releases of LTP to make the test suite faster and encourage upstream collaboration between kernel developers and test developers. Test maintainers reply to automated reports with their findings and the test suites (or the kernel) get patched.
LTP, blktests, and KVM unit tests find a lot of bugs on various architectures. Sometimes problems are found in other place, like zipl, the s390x bootloader.
And kudos to @gregkh for keeping the CKI team on their toes. :)pic.twitter.com/9PFFqZVK5D
Parsing emailed patches isn't easy. That's why the CKI team depends on Patchwork to extract patchsets from mailing list threads. https://patchwork.ozlabs.org/
But how do you do CI for the CI? Just reuse the same pipeline and let @gitlab CI and @openshift do it!pic.twitter.com/54HYkIlcth
Pipelines and triggers are already upstream: https://gitlab.com/cki-project Kernel tests are upstream, too: https://github.com/cki-project/tests-beaker … Test databases will be upstream soon as well. :)
Want to have your kernel tree tested? You can do it with a pull request to: https://gitlab.com/cki-project/pipeline-data … Need help? Email cki-project@redhat.com anytime. :)
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.