Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot delete the exec_directory in the epilogue #35

Closed
jgaida opened this issue Mar 11, 2016 · 1 comment
Closed

Cannot delete the exec_directory in the epilogue #35

jgaida opened this issue Mar 11, 2016 · 1 comment
Assignees

Comments

@jgaida
Copy link

jgaida commented Mar 11, 2016

The exec_directory cannot be deleted in the epilogue. I get the following error:

15420: (open) EPILOG_EXIT_ERROR of job 849 at 2016-03-11T10:50:34+01:00 on lyon
The job exited with exit status 256;

I believe this is because the output file of the epilogue job is stored in this directory.
Deleting the exec_directory after a campaign is rather useful when we would like to clean all output/temporary files of a campaign.

This issue has connections with #5 but even with a gridclean command, this issue should be fixed.

Example:

{
  "name": "Povray Landscape",  

  "resources": "nodes=1", 
  "walltime": "00:30:00", 
  "exec_file": "~/cigri/pov/pov.sh",
  "exec_directory": "$HOME/cigri/pov-tmp/",

  "nb_jobs": 4,

  "clusters": {   
    "lyon": {}
  },

  "epilogue": [
    "rm -rf ~/cigri/pov-tmp/"
  ]

}
@bzizou bzizou self-assigned this Mar 14, 2016
@bzizou
Copy link
Contributor

bzizou commented Mar 14, 2016

I think that the epilogue should be run from the home directory, like the prologue for a similar reason (the prologue is often used to create the working directory).

bzizou added a commit that referenced this issue Mar 14, 2016
The epilogue script should be able to remove the exec_directory
for cleaning, so it can't be run from it.
@bzizou bzizou closed this as completed Mar 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants