[Fuego] [Ksummit-discuss] Some ideas on open source testing
broonie at kernel.org
Mon Oct 24 16:41:16 UTC 2016
On Fri, Oct 21, 2016 at 09:19:25PM -0400, Theodore Ts'o wrote:
> And so you might have alarge number of workflows:
> * Developers who want a fast smoke test after applying a patch or
> patch set.
> * Developers who want to dig into a specific test failure, and who
> want to be able to very quickly iterate over running a specific test
> against a quick succession of test kernels.
> * Maintainers who want to run a much more comprehensive test suite
> that might take hours to run. * Release engineers who want some
> kind of continuous integration test.
> A test runner framework which is good for one is very likely not going
> to be good for another.
That's true but there's also an awful lot that can be shared - for
example, the mechanics of booting on a given system are going to be the
same regardless of how the test was scheduled or how long it will run
for. We should be looking for ways to share things as much as we can,
especially around the bits where the skills needed to implement align
less well with kernel skills.
[UI for reporting]
> I'm hoping to have an intern try to create something like that for
> gce-xfstests that would run on Google App Engine, over the next couple
> of months. So maybe by next year I'll have something that we'll be
> able to show off. We'll see....
This sort of UI thing seems like a prime example of an area where we
could really use some sharing - for example we've got some capacity to
run tests in kernelci but nobody to work on UI for doing anything useful
with the results.
> Maybe someday an ARM64 system will have the necessary hardware
> virtualization systems such that we can quickly test an ARM
> handset/embedded kernel using kvm on an ARM64 server / workstation.
Those systems are out there today, KVM works fine on arm64 providing
it's not been disabled - any of the server boards like Cavium or AMD
(both of which are orderable now) and a bunch of the embedded boards
like HiKey ought to be able to run it happily too.
> Maybe that would be a 90% solution for many file system and even
> device driver authors, assuming the necesary SOC IP blocks could be
> emulated by qemu.
qemu emulation isn't really that useful for driver testing, the quality
of the emulation with respect to the hardware is generally not super
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: not available
More information about the Fuego