Functions | |
| JobReport is the first of those Then black magic happens leading to the CFG command to the logger It happens in the statement std::auto_ptr< edm::EventProcessor > | procP (new edm::EventProcessor(processDesc, jobReportToken, edm::serviceregistry::kTokenOverrides)) |
| which instantiates a new passing | in (among other things) a vector of ParameterSet.ServicesManager has filled a list of"makers" |
| which instantiates a new passing done some complicated and called | CreateServices ().In CreateServices |
Variables | |
| Actions and Circumstances Relevant to Incomplete Log Problem The | Problem |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the | job |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger | does |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad | behavior |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to | debug |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code | Does |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread | joins |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described | here |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates | scribe |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after | that |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to | ServiceRegistry |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to retaining jobReportToken | Next |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to retaining jobReportToken the services are pushed onto | defaultServices |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to retaining jobReportToken the services are pushed onto with MessageLogger first Then the forcedServises are | created |
| which instantiates a new passing done some complicated | bookkeeping |
| which instantiates a new passing done some complicated and called itmaker invokes add on its second part The loop this is in is controlled by | requestedCreationOrder |
| JobReport is the first of those Then black magic happens leading to the CFG command to the logger It happens in the statement std::auto_ptr<edm::EventProcessor> procP | ( | new | edm::EventProcessorprocessDesc, jobReportToken, edm::serviceregistry::kTokenOverrides | ) |
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad behavior |
Definition at line 9 of file flush-and-end.txt.
Definition at line 49 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to retaining jobReportToken the services are pushed onto with MessageLogger first Then the forcedServises are created |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to debug |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to retaining jobReportToken the services are pushed onto defaultServices |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger does |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code Does |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described here |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the job |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread joins |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to retaining jobReportToken Next |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The Problem |
Definition at line 9 of file flush-and-end.txt.
| which instantiates a new passing done some complicated and called itmaker invokes add on its second part The loop this is in is controlled by requestedCreationOrder |
Definition at line 51 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates scribe |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after the jobReport is created on the heap and an auto_ptr to JobReport is given to ServiceRegistry |
Definition at line 9 of file flush-and-end.txt.
| Actions and Circumstances Relevant to Incomplete Log Problem The some of the LogInfo messages issued at the end involving branch information are failing to emerge This necessitates re running the for a net loss of up to of the work done The problem can t be happening based on what the logger but it is Dave Evans worte a stand along program to issue huge bunches of messages to try to provoke a repeatable version of the bad which we could hope to but could not get it to happen What the Current Code thread and end sequence actions are described theMessageServicePresence is instantiated The ctor of MessageServicePresence instantiates which is a instructing it to execute runMessageLoggerScribe Just after that |
Definition at line 9 of file flush-and-end.txt.
1.8.11
