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
Currently the deployed service (#348) takes feature engineered PR data as input, and yields the estimated time to merge of the PR as output. However, if this service is to be used by thoth / openshift-ci / other github bots, then it would probably only have the raw PR data (such as that collected via mi-scheduler) available. And therefore, it won't be able to yield any meaningful output.
One idea to remedy this issue is to update the deployed Pipeline object in the service to include feature engineering objects as well.
Currently the deployed service (#348) takes feature engineered PR data as input, and yields the estimated time to merge of the PR as output. However, if this service is to be used by thoth / openshift-ci / other github bots, then it would probably only have the raw PR data (such as that collected via mi-scheduler) available. And therefore, it won't be able to yield any meaningful output.
One idea to remedy this issue is to update the deployed Pipeline object in the service to include feature engineering objects as well.
Related to #236, #362
Acceptance Criteria
The text was updated successfully, but these errors were encountered: