You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo $?
28
belforte@lxplus825/bot> crab status -d crab_20241024_131730/
Rucio client intialized for account belforte
CRAB project directory: /afs/cern.ch/work/b/belforte/CRAB3/TC3/dbg/bot/crab_20241024_131730
Task name: 241024_111731:cmsbot_crab_20241024_131730
Grid scheduler - Task Worker: [email protected] - crab-preprod-tw01
Status on the CRAB server: KILLED
Task URL to use for HELP: https://cmsweb-testbed.cern.ch/crabserver/ui/task/241024_111731%3Acmsbot_crab_20241024_131730
Dashboard monitoring URL: https://monit-grafana.cern.ch/d/cmsTMDetail/cms-task-monitoring-task-view?orgId=11&var-user=cmsbot&var-task=241024_111731%3Acmsbot_crab_20241024_131730&from=1729765051000&to=now
Warning: Task killed by crab recover on '2024-10-24 14:17:38.506361', by 'cmsbot'
Status on the scheduler: COMPLETED
Jobs status: finished 100.0% (10/10)
The text was updated successfully, but these errors were encountered:
I decided to add a logger.info whenever there is a condition which leads to FAILED. It is more clear and flexible than do it in stepExit()
Now the existential question. If one types recover but there is nothing to do, do we end with exit code 0 ? Or with error ?
Already crab resubmit has a non-zero exit code when all jobs succeeded.
But we do not /can not check resubmit in ClientValidation.
Not only that, but
crab.log
has no useful information either [1]In addition, that makes ClientValidation test fail.
But in this case the failure is simply because there are no failed jobs to recover, everything was successful [2]
CRABClient/src/python/CRABClient/Commands/recover.py
Lines 73 to 74 in d145700
stepExit()
for this as the comment already indicated. Unless @mapellidario knows some reason why this is a bad idea !recover
never does thiscrab
command to have a non-zero exit code for situation where something bad happens. Or otherwise rewrite ClientValidation[1]
[2]
The text was updated successfully, but these errors were encountered: