Skip to content

Replicate Quantecon Execution Reporting #14

Open
@chrisjsewell

Description

@chrisjsewell

See: https://python.quantecon.org/status.html

This can be achieved by:

  1. Staging all notebooks for execution
  2. Running execution (which will only run for notebooks that don't exist in the cache)
  3. During/after execution, successfully executed notebooks will be committed to the cache
    with commit records containing data like execution_time (as implemented in Allow the executor to save data to the commit record. #13)
  4. During/after execution, failed notebooks would also be stored in the cache, in a separate
    folder, with a 'failure record' that's linked to the 'staged record' (not yet implemented). This will be deleted when the notebook is unstaged or execution re-run.
  5. Then, given a staged PK/URI, you can work out the build status, based on whether a complimentary commit/failure record exists, and retrieve any requisite data/notebooks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions