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
mantid-builder opened this issue
Mar 16, 2015
· 4 comments
Labels
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
When the remote algorithms are reorganized (http://trac.mantidproject.org/mantid/ticket/11126), FacilityInfo::getRemoteJobManager should not be needed any longer, and in general (I)RemoteJobManager should not be used in FacilityInfo.
Note: in http://trac.mantidproject.org/mantid/ticket/11126, rather than revamping the v1 remote algorithms breaking backwards compatibility, new version 2 remote algorithms have been introduced. Versions 1 still use getRemoteJobManager() and related chunks of code in FacilityInfo. So this ticket has to wait until the version 1 remove algorithms are removed (for which we could create a new ticket, or we could do it as part of this ticket).
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.
To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.
stalebot
added
the
Stale
This label is automatically applied to issues that are automatically closed by the stale bot
label
Feb 23, 2021
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
This issue was originally TRAC 11373
Original Reporter: @FedeMPouzols
This ticket is blocked by :
getRemoteJobManager()
is superseded by the RemoteJobManagerFactory (http://trac.mantidproject.org/mantid/ticket/11124).When the remote algorithms are reorganized (http://trac.mantidproject.org/mantid/ticket/11126), FacilityInfo::getRemoteJobManager should not be needed any longer, and in general (I)RemoteJobManager should not be used in FacilityInfo.
Note: in http://trac.mantidproject.org/mantid/ticket/11126, rather than revamping the v1 remote algorithms breaking backwards compatibility, new version 2 remote algorithms have been introduced. Versions 1 still use
getRemoteJobManager()
and related chunks of code inFacilityInfo
. So this ticket has to wait until the version 1 remove algorithms are removed (for which we could create a new ticket, or we could do it as part of this ticket).The text was updated successfully, but these errors were encountered: