Skip to content

Record execution order #19

Description

@joealcorn

When #13 was shipped we started running control & candidates in a random order. This is in order to weed out any issues caused by hidden dependencies between them.

However we never record the execution order anywhere, which could be a helpful piece of information when debugging these issues, so we should probably start doing that somehow.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions