You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Samuel E Bratton <sb...@us.ibm.com> on 2014/08/26 18:25:39 UTC
Guidelines on cleaning up tmp resources from builds?
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
Re: Guidelines on cleaning up tmp resources from builds?
Posted by Achim Nierbeck <bc...@googlemail.com>.
In that case make sure the tests do change the working dir in the config
method [1].
I usually use this:
workingDirectory("target/paxexam/"),
regards, Achim
[1] -
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/ITestBase.java#L62
2014-08-26 22:08 GMT+02:00 Samuel E Bratton <sb...@us.ibm.com>:
> 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 <bc...@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 <da...@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 <sb...@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
>
>
--
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
Re: Guidelines on cleaning up tmp resources from builds?
Posted by Samuel E Bratton <sb...@us.ibm.com>.
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 <bc...@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 <da...@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 <sb...@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
Re: Guidelines on cleaning up tmp resources from builds?
Posted by Achim Nierbeck <bc...@googlemail.com>.
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 <da...@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 <sb...@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
Re: Guidelines on cleaning up tmp resources from builds?
Posted by David Bosschaert <da...@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 <sb...@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