From: "Jan Beulich" <JBeulich@suse.com> To: Lars Kurth <lars.kurth.xen@gmail.com> Cc: Juergen Gross <jgross@suse.com>, xen-devel <xen-devel@lists.xenproject.org>, Ian Jackson <Ian.Jackson@eu.citrix.com>, committers@xenproject.org Subject: Re: Guest Testing in OSSTEST - What distros and versions should we test against Date: Fri, 10 May 2019 01:48:58 -0600 [thread overview] Message-ID: <5CD52CEA020000780022D6B1@prv1-mh.provo.novell.com> (raw) In-Reply-To: <9FCB2022-A547-4FA2-88E7-91DA3C023438@gmail.com> >>> On 10.05.19 at 03:28, <lars.kurth.xen@gmail.com> wrote: > Hi all, > > following a discussion with committers about Guest testing in OSSTEST, it > surfaced that we have not updated what distros we test in OSSTEST for a very > long time. All agreed that we should regularly review what we test against: > maybe at the beginning of a release cycle > > In any case, currently we test against > > x86 HVM guests: > debian-9.4.0-{i386,amd64}-CD-1.iso > rhel-server-6.1-i386-dvd.iso > win10v1703-x86.iso > win7-x64.iso > ws16-x64.iso > FreeBSD-10.1-CUSTOM-{i386,amd64}-20150525.raw.xz Testing fixed snapshots (commonly the original release afaict) instead of latest updates is pretty meaningless imo. While I would like to recommend testing all the (active) distros of parties actively involved in Xen development, I have to admite that I have no idea at all how this would work for e.g. our SLE versions (such that latest bits would get tested). > Debian HVM {i386,amd64} via debian-installer netinst [1] > > x86 PV guests: > Debian PV {i386,amd64} via debian-installer netinst [1] > > ARM guests: > Debian PV via debian-installer netinst [1] > > [1] whatever Debian release osstest itself mostly runs > > So I am opening the floor to suggestions. > > With regards to Windows testing we have some restrictions. We have tried > several times to buy additional test licenses, but this never went anywhere > (some of the VM licenses are not available for our environment, unless you > bulk buy, which is very expensive). The only approach that would allow us to > test against different windows versions would be to require everyone who may > touch OSSTEST which is not doable. > > I can bring this up with the MS open source office, if there are strong > feelings about this and try again If there's at least a (not overly) small chance of succeeding, I think this may be worth it, unless Rich's suggestion already helps. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com> To: "Lars Kurth" <lars.kurth.xen@gmail.com> Cc: Juergen Gross <jgross@suse.com>, xen-devel <xen-devel@lists.xenproject.org>, Ian Jackson <Ian.Jackson@eu.citrix.com>, committers@xenproject.org Subject: Re: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against Date: Fri, 10 May 2019 01:48:58 -0600 [thread overview] Message-ID: <5CD52CEA020000780022D6B1@prv1-mh.provo.novell.com> (raw) Message-ID: <20190510074858.Ws05BnR43VBoYXOromut1aPM2TOygLNzkZ2CX-vWF3w@z> (raw) In-Reply-To: <9FCB2022-A547-4FA2-88E7-91DA3C023438@gmail.com> >>> On 10.05.19 at 03:28, <lars.kurth.xen@gmail.com> wrote: > Hi all, > > following a discussion with committers about Guest testing in OSSTEST, it > surfaced that we have not updated what distros we test in OSSTEST for a very > long time. All agreed that we should regularly review what we test against: > maybe at the beginning of a release cycle > > In any case, currently we test against > > x86 HVM guests: > debian-9.4.0-{i386,amd64}-CD-1.iso > rhel-server-6.1-i386-dvd.iso > win10v1703-x86.iso > win7-x64.iso > ws16-x64.iso > FreeBSD-10.1-CUSTOM-{i386,amd64}-20150525.raw.xz Testing fixed snapshots (commonly the original release afaict) instead of latest updates is pretty meaningless imo. While I would like to recommend testing all the (active) distros of parties actively involved in Xen development, I have to admite that I have no idea at all how this would work for e.g. our SLE versions (such that latest bits would get tested). > Debian HVM {i386,amd64} via debian-installer netinst [1] > > x86 PV guests: > Debian PV {i386,amd64} via debian-installer netinst [1] > > ARM guests: > Debian PV via debian-installer netinst [1] > > [1] whatever Debian release osstest itself mostly runs > > So I am opening the floor to suggestions. > > With regards to Windows testing we have some restrictions. We have tried > several times to buy additional test licenses, but this never went anywhere > (some of the VM licenses are not available for our environment, unless you > bulk buy, which is very expensive). The only approach that would allow us to > test against different windows versions would be to require everyone who may > touch OSSTEST which is not doable. > > I can bring this up with the MS open source office, if there are strong > feelings about this and try again If there's at least a (not overly) small chance of succeeding, I think this may be worth it, unless Rich's suggestion already helps. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-10 7:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-10 1:28 Guest Testing in OSSTEST - What distros and versions should we test against Lars Kurth 2019-05-10 1:28 ` [Xen-devel] " Lars Kurth 2019-05-10 1:43 ` Rich Persaud 2019-05-10 1:43 ` [Xen-devel] " Rich Persaud 2019-05-24 21:26 ` Lars Kurth 2019-05-24 21:26 ` [Xen-devel] " Lars Kurth 2019-05-10 7:48 ` Jan Beulich [this message] 2019-05-10 7:48 ` Jan Beulich 2019-05-10 12:41 ` Lars Kurth 2019-05-10 12:41 ` [Xen-devel] " Lars Kurth 2019-05-27 11:56 ` Roger Pau Monné 2019-05-27 11:56 ` [Xen-devel] " Roger Pau Monné 2019-05-24 21:57 ` Lars Kurth 2019-05-24 21:57 ` [Xen-devel] " Lars Kurth
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5CD52CEA020000780022D6B1@prv1-mh.provo.novell.com \ --to=jbeulich@suse.com \ --cc=Ian.Jackson@eu.citrix.com \ --cc=committers@xenproject.org \ --cc=jgross@suse.com \ --cc=lars.kurth.xen@gmail.com \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.