Failed jobs classified as located in dbrailsf_gen_poms_test campaign stage.
An SBND productioner started to run a first campaign (dbrailsf_gen_poms_test) using sbndcode v06_69_00. It turns out that the fcl configuration is bugged for that version (incorrect service is set up). All of 10 jobs failed, as they should. However, those 10 jobs are reported as located. Located means that the output files are declared to SAM. Why failed jobs can be classified as located?
#1 Updated by Marc Mengel over 2 years ago
- Status changed from Assigned to Work in progress
- % Done changed from 0 to 90
We now have a Failed job and task status, which ends the workflow; at the moment the definition is Failed as defined in Success in the wiki; as
encoded in JobsFiles.py in the "failed_job" subroutine.
My main concern at the moment is that the cpu time threshold is too low -- we might use a few seconds of cpu time copying in scripts, etc. and still have a failed job... thus eb3f531.