That's enough of this, guys. There seems to be a lot of confusion (from every group) about whether processes are sitting idle or not. Everyone is burnt out and ready for summer, so let's make this nice and simple: don't leave idle processes when other groups are scheduled to do their work. On Sun, Apr 3, 2011 at 10:04 PM, Keo Malope <malopek@xxxxxxx> wrote: > I am not running any tests - just updating scripts. The processes are not > running, just idle. You should know that better than anyone because it's > your group's classic excuse for keeping your processes idle. > > Keo > > > > > On 3 April 2011 21:55, Cody Henschel <havoc@xxxxxxx> wrote: > >> Seriously. >> >> I dont care if the processes are idle. Don't start your programs when I >> am running my tests. The machines were just rebooted and group 2 has >> processes running all over the place. >> >> Get off the machines and let me run my test. You're effecting my tests >> which is effecting group 3 from getting theirs started. >> >> Cody Henschel >> >> > After the reboots I will be running some test for 2 hours. Please email >> > the list to see if I am done before starting. Thanks. >> > >> > >> > Cody Henschel >> > >> >> Reboots are incoming. >> >> >> >> On Sun, Apr 3, 2011 at 8:50 PM, Cody Henschel <havoc@xxxxxxx> wrote: >> >> >> >>> Again, we are testing, so please stop. >> >>> >> >>> >> >>> Cody Henschel >> >>> >> >>> > we are testing. Please refrain from starting before asking if we >> are >> >>> > done. It should only be for a couple hours but email us before >> >>> starting. >> >>> > >> >>> > Cody Henschel >> >>> > >> >>> >> Thanks for your patience guys >> >>> >> >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> >> >>> >> >>> >> >>> >> >> >> > >> > >> > >> >> >> >> >