Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339749 - Please remove workspace for cbi-wtp-wst.jsdt on "master"
Summary: Please remove workspace for cbi-wtp-wst.jsdt on "master"
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-11 14:03 EST by David Williams CLA
Modified: 2011-03-11 16:35 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2011-03-11 14:03:53 EST
The hudson job, cbi-wtp-wst.jsdt, has shown up on recent disk usage reports as taking up over a gig on 'master', example pasted below. 

I've been assured that the job is no longer configured to run on master, and that it typically only takes 50K or so ... and no one knows what is in there, but it can/should be deleted. 

As far as we can tell, the way to do this is to open a bug here? And webmaster can delete that workspace on master? 

= = = = = 


Compiled 2011-03-08T20:07

==== build.eclipse.org ====
-> Usage exceeding 1GB for: Hudson master jobs and workspace (2011-03-08T10:00)
...
   1.2G cbi-wtp-wst.jsdt
Comment 1 Eclipse Webmaster CLA 2011-03-11 14:53:28 EST
It looks like the issue isn't the workspace itself, rather the build directory within the job directory:

jobs/cbi-wtp-wst.jsdt # du -sh build
1.2G    build

If it's safe for me to delete the build directory I will.

-M.
Comment 2 David Williams CLA 2011-03-11 15:50:58 EST
(In reply to comment #1)
> It looks like the issue isn't the workspace itself, rather the build directory
> within the job directory:
> 
> jobs/cbi-wtp-wst.jsdt # du -sh build
> 1.2G    build
> 
> If it's safe for me to delete the build directory I will.
> 
> -M.

Sure. Its named 'build'? Not 'builds'? Not sure what that is ... but, is not being used. I'm wondering if there's any chance this could be created somehow by one of the regular builds on slave machine? By "accident" so to speak, perhaps during tests? Can you do a 'll' on that directory and/or a 'find' and list 10-20 entries, just so we can see what it is? Anything recent in there? (Like, from previous few weeks) or all months old (which is what would be expected)? 

Thanks,
Comment 3 Eclipse Webmaster CLA 2011-03-11 16:22:20 EST
obs/cbi-wtp-wst.jsdt/build # ls -fla
total 1
drwxr-xr-x 5 hudsonBuild callisto-dev  136 Jul 27  2010 .
drwxr-xr-x 5 hudsonBuild callisto-dev  288 Mar 10 12:38 ..
drwxr-xr-x 2 hudsonBuild callisto-dev  136 Jul 26  2010 downloads
drwxr-xr-x 3 hudsonBuild callisto-dev   72 Jul 26  2010 3rdPartyJars
drwxr-xr-x 6 hudsonBuild callisto-dev 1008 Jul 27  2010 athena
jobs/cbi-wtp-wst.jsdt/build # cd athena
jobs/cbi-wtp-wst.jsdt/build/athena # ls -Fla
total 81920
drwxr-xr-x  6 hudsonBuild callisto-dev     1008 Jul 27  2010 ./
drwxr-xr-x  5 hudsonBuild callisto-dev      136 Jul 27  2010 ../
-rw-r--r--  1 hudsonBuild callisto-dev    16533 Jul 27  2010 build.cfg
-rw-r--r--  1 hudsonBuild callisto-dev     2177 Jul 27  2010 build.cfg.test
drwxr-xr-x  3 hudsonBuild callisto-dev      136 Jul 27  2010 compilelogs/
-rw-r--r--  1 hudsonBuild callisto-dev     4802 Jul 27  2010 directory.txt
-rw-r--r--  1 hudsonBuild callisto-dev    20017 Jul 27  2010 echoproperties-build.xml-all.txt
-rw-r--r--  1 hudsonBuild callisto-dev    20020 Jul 27  2010 echoproperties-build.xml-tests.txt
drwxr-xr-x 11 hudsonBuild callisto-dev     4416 Jul 27  2010 eclipse/

So it's all pretty old.  Find doesn't return anything for 1,2,30 or 60 days ago.

-M.
Comment 4 David Williams CLA 2011-03-11 16:28:27 EST
> 
> So it's all pretty old.  Find doesn't return anything for 1,2,30 or 60 days
> ago.
> 

Sounds good. As expected ... can be safely deleted.
Comment 5 Eclipse Webmaster CLA 2011-03-11 16:35:13 EST
Done.

-M.