Skip to content

Configure job timeout properly #49

@Eoghan-Perkins

Description

@Eoghan-Perkins

Currently the algorithm will run for 6 minutes straight and then time out. This might not be enough time for "historical" jobs that have a couple hour long timebox to process. Should probably offer a dynamic timeout that is 6 minutes for "now" jobs, but if certain time parameters are passed in, a linearly interpolated timeout will be produced and passed to the algorithm runner, taking the duration of the timebox as a parameter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions