Successful kinckstart installs?

2014-05-27 Thread Gene Czarcinski
Has anyone gotten a successful kickstart install with current rawhide? With the smae ks file (except using eth0 for the network device), a Fedora 20 kickstart install completed nicely. Doing the "same" (ens3 instead of eth0) kickstart with rawhide 5/27/2014 DVD iso, it completely ignored the

Re: Fedora.next QA planning: generic / Product-specific release criteria and blocker review issues

2014-05-27 Thread Mike Ruckman
On Tue, 27 May 2014 18:22:21 -0700 Adam Williamson wrote: > Hi, folks. So continuing with the theme of setting up the Fedora.next > QA process, I thought before going too far with draft release > criteria etc, we could discuss a couple of important points that have > come up since I sent out the

Re: rawhide20140523 boot.iso fails, kernel versions

2014-05-27 Thread Gene Czarcinski
On 05/27/2014 12:56 AM, Chris Murphy wrote: On May 23, 2014, at 12:46 PM, Adam Williamson wrote: I don't really find them 'astronomically' slow any more, now that slub_debug is left off most of the time. Slightly slower than regular kernels, sure, but perfectly fine for testing. Is it different

Fedora.next QA planning: generic / Product-specific release criteria and blocker review issues

2014-05-27 Thread Adam Williamson
Hi, folks. So continuing with the theme of setting up the Fedora.next QA process, I thought before going too far with draft release criteria etc, we could discuss a couple of important points that have come up since I sent out the draft test plan. There are two kind of similar issues in particular

Re: Draft Fedora 21 Test Plan

2014-05-27 Thread Matthew Miller
On Tue, May 27, 2014 at 12:58:12PM -0700, Adam Williamson wrote: > As with all the others who've weighed in so far, I agree that the > optimal path is just for us all to talk to each other. I generally > prefer workflows that assume everyone's happy to work positively > together to a consensus solu

Re: Draft Fedora 21 Test Plan

2014-05-27 Thread Adam Williamson
On Tue, 2014-05-27 at 07:58 -0400, Matthew Miller wrote: > On Fri, May 23, 2014 at 06:02:07PM -0700, Adam Williamson wrote: > > Hi, folks! So, I quickly bashed out that draft F21 Test Plan I've been > > threatening to write for the last month or so. > > https://fedoraproject.org/wiki/User:Adamwill/

Re: Draft Fedora 21 Test Plan

2014-05-27 Thread Mike Ruckman
On Tue, 27 May 2014 07:58:55 -0400 Matthew Miller wrote: > > Yeah. If something isn't working, do you think the best path is QA->WG > directly, or should it be QA says something to FESCo, FESCo works > with WG? > > Since parts of this are new to all of us, and other parts new to a > lot of us,

Re: Draft Fedora 21 Test Plan

2014-05-27 Thread Josh Boyer
On Tue, May 27, 2014 at 7:58 AM, Matthew Miller wrote: > On Fri, May 23, 2014 at 06:02:07PM -0700, Adam Williamson wrote: >> for Fedora 21 testing *overall* - i.e. it's the QA team's responsibility >> to make sure the WGs do the stuff assigned to them in the plan. If that >> makes sense. Discussio

Re: Draft Fedora 21 Test Plan

2014-05-27 Thread Matthew Miller
On Fri, May 23, 2014 at 06:02:07PM -0700, Adam Williamson wrote: > Hi, folks! So, I quickly bashed out that draft F21 Test Plan I've been > threatening to write for the last month or so. > https://fedoraproject.org/wiki/User:Adamwill/Draft_Fedora_21_test_plan > So, what's the idea here? Psshh -- s

Re: Test Plan location for 389

2014-05-27 Thread Amita Sharma
On 05/27/2014 05:27 AM, Adam Williamson wrote: On Sun, 2014-05-25 at 18:49 +0530, Amita Sharma wrote: Thanks for explaining the things so nicely, I hope I got it right and updated the stuff accordingly. Please check :: 1. http://fedoraproject.org/wiki/Category:Test_Cases - New Category 3 2. htt

Rawhide refression

2014-05-27 Thread Chuck Forsberg WA7KGX
Monday's rawhide has reverted to a sluggish desktop and a number of kernel OOPs on my office machine. I upgraded my office machine to a PNY Geforce GTX780TI. The card has been out since November. Fry's is selling it at a discount. Windows 7 found updated drivers automatically. The Nvidia driver