persisting job_working_directory
Hello, I am building a tool for galaxy and am trying to debug it. I am using the latest central. When I run my tool I see a directory created under job_working_dir, containing my logs and such generated by my tool. However, this directory is deleted within a couple seconds of the job finishing. I have been searching for the config option to persist these working dirs but to no avail. I seem to find hints that these directories stick around for other folks. What am I missing? Thanks, Darren
Darren, There isn't a configuration option for controlling this, but the quick fix for your own use while developing tools would be to comment out the lines in the cleanup method of the JobWrapper that handle removal of the directory. The change should be near line 641 of lib/galaxy/jobs/__init__ .py, these two lines: if self.working_directory is not None and os.path.isdir( self.working_directory ): shutil.rmtree( self.working_directory ) -Dannon On Jan 9, 2011, at 5:45 AM, Darren Brown wrote:
Hello,
I am building a tool for galaxy and am trying to debug it. I am using the latest central. When I run my tool I see a directory created under job_working_dir, containing my logs and such generated by my tool. However, this directory is deleted within a couple seconds of the job finishing. I have been searching for the config option to persist these working dirs but to no avail. I seem to find hints that these directories stick around for other folks. What am I missing?
Thanks,
Darren _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
participants (2)
-
Dannon Baker
-
Darren Brown