Hi Neil, thanks for sharing your interesting plans and sorry for the late reply... On Freitag, 20. Februar 2015, Neil Williams wrote: > > what is this lava stuff? > https://packages.debian.org/jessie/lava-server > Continuous integration system currently in use for kernel and > bootloader testing on ARM but open to other architectures as well. [...] [...] > Debian has a number of QA tasks based around individual packages but > little support for QA tasks involving architectures other than amd64, that's absolutly the case and I'm glad you are working on improving these areas. which reminds me to point out: piuparts.d.o shall be extended this year to test other architectures as well. Help on this is much welcome, I'd be glad to mentor and I know Andreas has some patches flying around - but still, someone new working on this would be awesome and I'd be really glad to get her or him started. That said, hardware offers for non-x86 and !ppc64 piuparts-slaves would also be very welcome...! > tasks involving multiple packages interacting or disparate systems or > reproducible testing of large scale upgrades. jenkins.d.n has 384 tests (involving 5 debian suites) in the category chroot- installations, which also tests installations and upgrades of package combinations, see https://jenkins.debian.net/view/chroot-installation/ do you have ideas what to add? > > > Debian Installer test parallelisation on x86 and ARM - utilise > > > support from FAI to completely automate testing of DI, possibly > > > including support for video capture cards (where hardware is > > > available). > > FAI as in fully automatic install or something else? > Yes, fully automatic install so that DI builds can be tested on lots of > different devices at the same time, automatically. so FAI as in "fully automatic install" but not as in src:fai in Debian? that's confusing. > What has become apparent within the LAVA usage is that LAVA is one > piece of a solution for implementing CI in this way. Once the results > are available, the data needs to be presented in a way that is relevant > to one specific audience. Teams are now using LAVA as the data source > and building custom frontends to be able to close the CI loop and get > relevant information back to developers in as short a timeframe as > possible, directly after commits or merges. e.g. http://kernelci.org/ > > So something like ci.debian.net could incorporate this data or another > frontend could be designed which collates the raw LAVA data into a > format suitable and meaningful to Debian folk. hm, I see. So somewhat similar to reproducible.debian.net which basically is just a collection of static pages created by jenkins.d.n :) > What I'd be looking for from a sprint like this is to create a team > willing to work on providing this frontend and a collection of people > willing to run tests on hardware already available. This would include > devices which are currently available via Linaro, just as kernelci.org > does. The sprint would also cover what kind of tests people want to run > and how the results should be presented. Nice. I'd might hang around, just because I like QA ;-) > The new dispatcher which would run the tests is in development and > won't be complete by this DebConf, however, enough is expected to be > available to allow initial design. good luck with your plans! :) cheers, Holger
Attachment:
signature.asc
Description: This is a digitally signed message part.