-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Sometimes, the epilogue fails but the campaign is considered as "terminated".
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": 5,
"prologue": [
"mkdir -p ~/cigri/pov/",
"rsync -avz lyon:~/cigri/pov/ ~/cigri/pov/",
"mkdir -p ~/cigri/pov-tmp/"
],
"epilogue": [
"rsync -avz --update --exclude='OAR.cigri.*' ~/cigri/pov-tmp/ lyon:~/cigri/pov-results/",
"rm ~/cigri/pov-tmp/*.png"
],
"clusters": {
"lyon": {
"prologue": [
"mkdir -p ~/cigri/pov-tmp/"
]
},
"nancy": {}
}
}
jgaidamour@flyon:~$ gridevents 29
No events!
jgaidamour@flyon:~$ gridstat 29
Campaign: 29
Name: Povray Landscape
User: jgaidamour
Date: 2016-03-11 14-34-06
State: terminated
Progress: 5/5 (100%)
Stats:
average_jobs_duration: 13.6
stddev_jobs_duration: 1.51657508881031
jobs_throughput: 2250.0 jobs/h
remaining_time: 0.0 hours
failures_rate: 0.0 %
resubmit_rate: 0.0 %
Clusters:
lyon:
active_jobs: 0
queued_jobs: 0
prologue_ok: true
epilogue_ok: false
nancy:
active_jobs: 0
queued_jobs: 0
prologue_ok: true
epilogue_ok: false
I cannot find the log of the epilogue. In addition, the log of the prologue are located in $HOME (instead of $HOME/cigri/pov-tmp/ ?).
It should be possible to re-run the epilogue and the campaign should have open events.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels