[jbosscache-dev] Re: Jboss Cache CC

[Galder Zamarreno]

This one:

"The other alternative is to include a separate log4j.cc.xml in CVS and point the ant task to use this configuration (via the - Dlog4j.configuration property) for CC runs."

Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat

IT executives: Red Hat still #1 for value http://www.redhat.com/promo/vendor/

-----Original Message-----
From: jbosscache-dev-bounces at lists.jboss.org [mailto:jbosscache-dev-bounces at lists.jboss.org] On Behalf Of Manik Surtani
Sent: 15 January 2007 11:34
To: Ryan Campbell
Cc: QA; jbosscache-dev at lists.jboss.org
Subject: [jbosscache-dev] Re: Jboss Cache CC

Man - this is crap that there is so much logging going on.  By  
default we ship with log4j.xml configured to log at INFO level, and  
this is what is in CVS.

Does anyone have any objections to my setting it to ERROR before  
checking it into CVS, so CC runs perform tests with ERROR level  
logging?  In addition to taking up less disk space it would also mean  
much quicker runs.

It would mean an additional release task of setting this to INFO  
before releasing though, but I think this is reasonable.

The other alternative is to include a separate log4j.cc.xml in CVS  
and point the ant task to use this configuration (via the - 
Dlog4j.configuration property) for CC runs.

Which do people prefer?
--
Manik Surtani

Lead, JBoss Cache
JBoss, a division of Red Hat

Email: manik at jboss.org
Telephone: +44 7786 702 706
MSN: manik at surtani.org
Yahoo/AIM/Skype: maniksurtani



On 15 Jan 2007, at 03:37, Ryan Campbell wrote:

> This is the problem:
>
> -rw-rw-r--   1 cruisecontrol cruisecontrol 134848512 Jan 14 03:24
> jbosscache.log
> -rw-rw-r--   1 cruisecontrol cruisecontrol 193673415 Jan  5 04:06
> jbosscache.log.2007-01-05
> -rw-rw-r--   1 cruisecontrol cruisecontrol 114693620 Jan  6 02:48
> jbosscache.log.2007-01-06
> -rw-rw-r--   1 cruisecontrol cruisecontrol 124116582 Jan  7 03:00
> jbosscache.log.2007-01-07
> -rw-rw-r--   1 cruisecontrol cruisecontrol 222840969 Jan  8 07:24
> jbosscache.log.2007-01-08
> -rw-rw-r--   1 cruisecontrol cruisecontrol 211811326 Jan  9 06:58
> jbosscache.log.2007-01-09
> -rw-rw-r--   1 cruisecontrol cruisecontrol 186563185 Jan 10 05:51
> jbosscache.log.2007-01-10
> -rw-rw-r--   1 cruisecontrol cruisecontrol 166926968 Jan 11 04:12
> jbosscache.log.2007-01-11
> -rw-rw-r--   1 cruisecontrol cruisecontrol 465786953 Jan 13 12:02
> jbosscache.log.2007-01-13
>
> This is being written to /tmp which is being filled up.  It needs  
> to be
> written to output/logs instead.  Can you guys fix this?
>
> I've deleted the existing logs.
>
>> -----Original Message-----
>> From: Vladimir Blagojevic
>> Sent: Sunday, January 14, 2007 8:38 PM
>> To: Ryan Campbell
>> Cc: 'Manik Surtani'
>> Subject: RE: Jboss Cache CC
>>
>> Ryan,
>>
>> Thanks. It worked for a day but looking at the latest logs it seems
> like
>> CC machine does not have disk space anymore.
>>
>> http://cruisecontrol.jboss.com/cc/artifacts/jboss-cache-
>> testsuite/20070114011906/tests.log
>>
>>
>> Cheers,
>> Vladimir
>>
>>> -----Original Message-----
>>> From: Ryan Campbell
>>> Sent: Sunday, January 14, 2007 9:29 PM
>>> To: Vladimir Blagojevic; QA
>>> Cc: 'Manik Surtani'
>>> Subject: RE: Jboss Cache CC
>>>
>>> Sorry for the delay, I believe this was due to a restart of
>>> cruisecontrol.
>>>
>>>> -----Original Message-----
>>>> From: Vladimir Blagojevic
>>>> Sent: Friday, January 12, 2007 10:04 AM
>>>> To: QA
>>>> Cc: Manik Surtani
>>>> Subject: Jboss Cache CC
>>>>
>>>> Hey guys,
>>>>
>>>> Would you please look at the reason why Jboss Cache
>>> testsuite did not
>>>> run on CC last night. Last time it ran was a day ago [1].
>>> Since then
>>>> we made some changes to a build process where a testsuite
>>> now should
>>>> run twice as long as usual - for about 180 minutes. It ran
>>> ok locally on my machine.
>>>>
>>>> Much appreciated,
>>>> Vladimir
>>>>
>>>>
>>>>
>>>> [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-
>>>> testsuite?log=log20070111023624
>>>>
>>>> -----Original Message-----
>>>> From: Manik Surtani [mailto:manik at jboss.org]
>>>> Sent: Friday, January 12, 2007 10:58 AM
>>>> To: Vladimir Blagojevic
>>>> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>>>>
>>>> Ping QA.  They may have server issues
>>>>
>>>> --
>>>> Manik Surtani
>>>>
>>>> Lead, JBoss Cache
>>>> JBoss, a division of Red Hat
>>>>
>>>> Email: manik at jboss.org
>>>> Telephone: +44 7786 702 706
>>>> MSN: manik at surtani.org
>>>> Yahoo/AIM/Skype: maniksurtani
>>>>
>>>>
>>>>
>>>> On 12 Jan 2007, at 15:20, Vladimir Blagojevic wrote:
>>>>
>>>>> Nothing I can find. I did not get notificatin email. There is no
>>>>> trace that the build ran at all...
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Manik Surtani [mailto:manik at jboss.org]
>>>>>> Sent: Friday, January 12, 2007 9:49 AM
>>>>>> To: Vladimir Blagojevic
>>>>>> Cc: Brian Stansberry; jbosscache-dev at lists.jboss.org
>>>>>> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>>>>>>
>>>>>> Nothing in the compile log?
>>>>>> --
>>>>>> Manik Surtani
>>>>>>
>>>>>> Lead, JBoss Cache
>>>>>> JBoss, a division of Red Hat
>>>>>>
>>>>>> Email: manik at jboss.org
>>>>>> Telephone: +44 7786 702 706
>>>>>> MSN: manik at surtani.org
>>>>>> Yahoo/AIM/Skype: maniksurtani
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 12 Jan 2007, at 14:41, Vladimir Blagojevic wrote:
>>>>>>
>>>>>>>
>>>>>>> Hmm. Build report is missing! Locally it worked for me and
>>>>>> the suite
>>>>>>> ran for about 180 minutes. Report looked good,
>>> everything was fine.
>>>>>>> Wonder why is it missing?
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>

_______________________________________________
jbosscache-dev mailing list
jbosscache-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev