Re: new project: taskotron-vmbuilder

2015-05-04 Thread Kamil Paral
> On Wed, 2015-04-29 at 11:21 -0400, Kamil Paral wrote: > > > > I still haven't created project and repo in Phab, but if you approve > > this as a way forward, I will. > > Just one thought - this could probably be rather useful for openQA > too. We already have one case where we want to begin a t

Re: new project: taskotron-vmbuilder

2015-05-04 Thread Adam Williamson
On Wed, 2015-04-29 at 11:21 -0400, Kamil Paral wrote: > > I still haven't created project and repo in Phab, but if you approve > this as a way forward, I will. Just one thought - this could probably be rather useful for openQA too. We already have one case where we want to begin a test with a sp

WhenIsGood - Scheduling a discussion around Fedora Projects Planning

2015-05-04 Thread Adam Miller
Hello all, There was recently a discussion on the Fedora Rel-Eng list as the result of a Project Planning workflow[0]. As this was discussed further in irc it was decided that this is likely a conversation that should be had across more Fedora groups to see if there's a solution that we would a

Re: 22 Final TC1 live fail: timeout due to SMP performance bug?

2015-05-04 Thread Kamil Paral
> > https://bugzilla.redhat.com/show_bug.cgi?id=1210857 , but I see > > you've found it already. > > > > For the time being, it seems that there's no benefit in giving the > > VMs more than one CPU? > > Yeah, I think it'd make sense to change the config to one CPU. That's > what I use on openqa.h

2015-05-04 Fedora QA Devel Meeting Minutes

2015-05-04 Thread Tim Flink
== #fedora-meeting-1: qadevel == Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2015-05-04/qadevel.2015-05-04-14.07.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2015-05-04/qadevel.2015-05-04-14.07.txt Log: htt

Re: new project: taskotron-vmbuilder

2015-05-04 Thread Tim Flink
On Wed, 29 Apr 2015 11:21:10 -0400 (EDT) Kamil Paral wrote: > There are sample templates for minimal installation and Server and > Workstation products. For more details, look into READMEs, it's > fairly well documented, I think. My idea is that we will run this > daily on the server, store the