2.1.24 (1)

• A secondary patch is needed for job report interpretation; the pilot should now handle the cases below. The case (7) when nentries = null / None was not handled correctly and led to some failures of jobs where the output file verification should have been "successful", ie the case should be ignored
  1. No output files in the job definition (abort output file verification)
  2. Output info is an empty list (consult with allowNoOutput list; fail job is output file is not present in that list, otherwise remove file from stage-out and approve verification)
  3. Output info is entirely missing (ignore output file verification)
  4. Output nentries are missing but output info exists (ignore validation)
  5. nentries is an int (good)
  6. nentries is 0 (consult with allowNoOutput list; fail job is output file is not present in that list, otherwise remove file from stage-out and approve verification)
  7. nentries is null or None (ignore validation if file is not in allowNoOutput; otherwise remove file from stage-out and approve verification)
  8. nentries is a string; only known value: “UNDEFINED” (ignored)
  9. any other cases will be ignored (ie output file verification will be approved)
• Pilot is now recognising the following stderr message patterns for all combinations of ‘ERROR:’, ’Error:’, ‘error:’, ‘WARNING:’, ‘Warning:’, ‘warning:’ plus optional extra space before the ‘:’. The previous version only recognised some of these which meant that the primary failure was missed in some cases and the secondary error was instead reported (e.g. HC tests using bad job options)