Implement Workflow Scheduling Test Cases

[jmchilton]

• Make sure that cancelling a job that is causing workflow scheduling to delay, cancels the workflow scheduling.
• Make sure that a job failing that is causing workflow scheduling to delay, fails the workflow scheduling.
• Make sure that deleting a history that a workflow is scheduled to run against, cancels workflow scheduling.

[nsoranzo]

Make sure that deleting a history that a workflow is scheduled to run against, cancels workflow scheduling.

This keeps happening on 17.05:

galaxy=> SELECT workflow_invocation.id AS wfi_id, workflow_invocation.state AS wfi_state, history.id as hid, history.name AS history_name, history.deleted FROM workflow_invocation JOIN history ON workflow_invocation.history_id = history.id WHERE history.deleted IS TRUE AND workflow_invocation.state NOT IN ('failed', 'scheduled') ORDER BY wfi_id;
 wfi_id | wfi_state | hid |            history_name             | deleted 
--------+-----------+-----+-------------------------------------+---------
    800 | ready     | 821 | GeneSeqToFamily on 23 and 22        | t
...
(13 rows)

An admin can fix them by running the following SQL query:

UPDATE workflow_invocation SET state = 'failed' WHERE id IN (SELECT workflow_invocation.id FROM workflow_invocation JOIN history ON workflow_invocation.history_id = history.id WHERE history.deleted IS TRUE AND workflow_invocation.state NOT IN ('failed', 'scheduled'));

[jmchilton]

Ping @RJMW...

I'd modify this a bit for your purposes and kill just the one invocation from your logs:

UPDATE workflow_invocation SET state = 'failed' WHERE id = 2;

[bgruening]

Had this problem again with 17.09.

[martenson]

I am clearing the milestone here.