On Mon, Feb 24, 2020 at 10:36:54PM +0530, Naresh Kamboju wrote: > Hi Paolo, > > On Mon, 24 Feb 2020 at 18:36, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > > > On 24/02/20 13:53, Naresh Kamboju wrote: > > > FAIL vmx (408624 tests, 3 unexpected failures, 2 expected > > > failures, 5 skipped) > > > > This could be fixed in a more recent kernel. > > I will keep running these tests on most recent kernels. > > My two cents, > OTOH, It would be great if we have monthly tag release for kvm-unit-tests. > > LKFT plan to keep track of metadata / release tag version of each test suites > and kernel branches and versions details. > > Currently LKFT sending out kselftests results test summary on > each linux-next release tag for x86_64, i386, arm and arm64 devices. > > The next plan is to enable kvm-unit-tests results reporting from LKFT. Rather than monthly tags, what about tagging a release for each major kernel version? E.g. for v5.5, v5.6, etc... That way the compatibility is embedded in the tag itself, i.e. there's no need to cross reference release dates against kernel/KVM releases to figure out why version of kvm-unit-tests should be run. Paolo more or less agreed to the idea[*], it's just never been implemented. [*] https://lkml.kernel.org/r/dc5ff4ed-c6dd-74ea-03ae-4f65c5d58073@xxxxxxxxxx
