aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samuel E Bratton <sbrat...@us.ibm.com>
Subject Re: Guidelines on cleaning up tmp resources from builds?
Date Tue, 26 Aug 2014 20:08:38 GMT
Yes, a large chunk of the left-over tmp data does seem related to 
pax-exam.  They are files like /tmp/stdout163431288163096157deferred and 
are blueprint-itest logs.

I didn't see obvious logging config differences that account for this, 
when comparing blueprint and other components that don't create the tmp 
files. 



From:   Achim Nierbeck <bcanhome@googlemail.com>
To:     dev@aries.apache.org
Date:   08/26/2014 11:33 AM
Subject:        Re: Guidelines on cleaning up tmp resources from builds?



Without looking at the tests,
but might be because of Pax Exam, if not configured differently it will
write certain data to a system temp folder.

regards, Achim


2014-08-26 18:29 GMT+02:00 David Bosschaert <david.bosschaert@gmail.com>:

> I agree that builds shouldn't leave anything behind outside of the
> maven target directory. If it uses tmp space elsewhere, this should be
> cleaned up after use.
>
> Cheers,
>
> David
>
> On 26 August 2014 17:25, Samuel E Bratton <sbratton@us.ibm.com> wrote:
> > Hi
> >
> > I noticed that a full aries build leaves ~70MB in /tmp  (about 85% of
> that
> > appears to be from blueprint-itest related logs and from OSGI
> workspaces).
> >
> > I know some systems automatically clean out tmp periodically, but for
> > those that do not, shouldn't component builds be cleaning up those
> > resources on their own?
> >
> > Thanks
> > Sam Bratton
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>

Software Architect / Project Manager / Scrum Master


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message