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
QC-1132 Correct validity in PostProcessingTasks across run restart (#2190)
This makes sure that the SOR&EOR timestamps are retrieved from ECS and passed to the user task with UserOrControl trigger, but they are not used to establish the validity of produced objects.
Also, we do not publish objects if the validity is going to be invalid, since they will not be stored anyway.
We produce appropriate warnings in such case.
The root cause for having EOR timestamp earlier than SOR for the 2nd run was discovered to come from ECS sending incorrect values.
However, with this commit, these values will not be used anyway for determining objects validity.
// TODO: we could consider using SOR, EOR as validity in such case, so empty objects are still stored in the QCDB.
308
+
ILOG(Warning, Devel) << "Objects will not be published because their validity is invalid. Most likely the task's update() method was never triggered." << ENDM;
auto partitionName = services.get<framework::RawDeviceService>().device()->fConfig->GetProperty<std::string>("environment_id", fallbackActivity.mPartitionName);
71
71
auto periodName = services.get<framework::RawDeviceService>().device()->fConfig->GetProperty<std::string>("lhcPeriod", "");
0 commit comments