> -----Original Message----- > From: xsce-de...@googlegroups.com [mailto:xsce- > de...@googlegroups.com] On Behalf Of Jerry Vonau > Sent: Sunday, November 15, 2015 12:24 PM > To: Anish Mangal <anis...@umich.edu>; xsce-de...@googlegroups.com > Cc: server-devel <server-devel@lists.laptop.org> > Subject: Re: [XSCE] [RFC] XSCE 6.0 test matrix > > > > > On November 15, 2015 at 10:27 AM Anish Mangal <anis...@umich.edu> > wrote: > > > > > > On Sun, Nov 15, 2015 at 9:46 PM, Tim Moody <t...@timmoody.com> > wrote: > > > > > What does install mode mean? (gateway, appliance, nw controller?) > > > > > > > > > > > > > Yes > > > > Should we add a starting point as in pre-packaged image, older vm, fresh vm, > fresh stock net/livecd install, or my kickstart assisted install? Did I > miss any flavors of starting points?
I think the whole question of test methodology has not yet been addressed, but this is certainly an aspect of it. > > > > > > I added Number Eth adapters and other HW info > > > > > > > > > > > > > Great. I was actually thinking whether we should have different rows > > for all such info, or just a link to /etc/xsce.ini. Maybe it makes > > sense to have them in separate rows just in case the info in > > /etc/xsce,ini may be stale? > > > > > > > what do L0 and L1 mean? > > > > > > > > > > > > > This is a remnant of my semiconductor h/w verification days. Wanted to > > have a basic distinction between depth of testing. So in this case, L0 > > would mean basic testing of the most critical stuff. L1 means deeper > > level testing. The idea being an L0 test run would be over much > > quicker and L1 take additional time (and maybe expertise) so not > > everybody might want to do it. > > I like the idea. Just to clarify, are you thinking if the correct result > appears in > L0 there should be no need to move to L1's more detailed debugging? > > Jerry _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
