joealcorn/laboratory

Record execution order

Open

#19 opened on Aug 1, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (1,248 stars) (32 forks)batch import
enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
python
Domain
developer experiencetesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Pythonlogging conceptsfamiliarity with laboratory library
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the execution logic in the laboratory library, likely in the main experiment runner (e.g., `laboratory/experiment.py`). Locate where control and candidate experiments are run, and add a logging statement to record the order of execution. Use Python's logging module to emit the sequence. Check existing tests to ensure consistency. Refer to issue #13 for context on the random ordering change.