On Thu, Feb 16, 2017, at 12:01 PM, Adam Williamson wrote:
> Glad to see you thinking about this. openQA also has desktop tests
> which we could certainly run on Atomic Workstation images;
This is somewhat of a tangent but I was just thinking that openQA
tests the installer *only*. One of the whole major goals of this is
that by using rpm-ostree to assemble content on the server side,
*that* is the base of the compose (plus any apps/containers to test) Which means that it's
very valid to have a cached set of existing systems, and do in-place upgrades,
rather than doing fresh installs each time. Because of the image-based
nature of ostree, one can have a high degree of confidence that the result
of an update is exactly identical to a fresh install[1].
While you've done a lot of heroics maintaining needles for openCV, and
it does make sense to test the installer that way (particularly since
the installer is almost identical, we can share most of that across products),
I'd like to have a variety of systems that test the ostree commit via a mix of inplace
updates and fresh installs, like we do for Atomic Host.
So I guess this isn't really a tangent at all - the concept that the system
is assembled as a unit with a checksum, version etc., which is what
becomes the fundamental unit of test is actually a major goal of
doing this - it makes the system very different in practice from
other systems which snapshot packages on the client side.
[1] Although since ostree operates on the filesystem and not block layer,
it means systems use retain their initial filesystem layout, we can't
upgrade that layer; - this bit us for Atomic Host with XFS + f_type + overlayfs:
https://bugzilla.redhat.com/show_bug.cgi?id=1288162#c8
_______________________________________________
desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
