Project

General

Profile

Support #11152

services.scheduler.errorOnFailureToPut should default to true

Added by John Freeman over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/15/2015
Due date:
% Done:

100%

Estimated time:
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

The lariat-online code broke when it switched over to art v1_17_03 , and I found that to fix it I needed to add the "errorOnFailureToPut" variable to services.scheduler. To see exactly what I did, if you check out lariat-online you can do the following:

git diff 656c7033f2adf26efafdfc482e77aa396b400050 6f158e82bd64962beb725fa69a7265d82a96f4b7 -- daq/lariat-artdaq/tools/fcl/Aggregator1_for_Lariat_1x1x2.fcl

although really, the relevant info here is that I changed

 services: {
   scheduler: {
     fileMode: NOMERGE
   }
.
.
.

to

services: {
   scheduler: {
     fileMode: NOMERGE
     errorOnFailureToPut: true
   }
.
.
.

I realize that this was added as a way to address Issue 7852 ; however, it seems to me that while it's reasonable to allow users whose code doesn't conform to the new requirements to be able to turn off the requirement by setting "errorOnFailureToPut: false", users whose code already conforms to the requirements shouldn't see their code break because of this parameter. Would it be possible to have this variable default to true, without it needing to be set explicitly?

History

#1 Updated by Kyle Knoepfel over 3 years ago

  • Status changed from New to Feedback

The services.scheduler.errorOnFailureToPut flag is set to true by default for any art job that uses the standard artapp executable. I wonder if you're running into the same problem that Eric Flumerfelt ran into a couple weeks ago--see issue #10972-5. Please let us know if your situation is different than the one described there.

#2 Updated by John Freeman over 3 years ago

Very interesting - issue #10972 does indeed describe the same phenomenon. In light of this, I don't think this issue will add anything to the discussion presented in #10972, so consider it closed.

#3 Updated by Kyle Knoepfel over 3 years ago

  • Tracker changed from Feature to Support
  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100
  • SSI Package art added
  • SSI Package deleted ()

Thanks, John. Closed it is.



Also available in: Atom PDF