JuliaParallel/Dagger.jl

Implement chaos testing framework

Open

#211 opened on Apr 20, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Julia (706 stars) (86 forks)batch import
cifault handlinghelp wanted

Description

As the scheduler grows more optimizations, options, and supported features, the combination of configurations that the scheduler needs to handle correctly grows exponentially. We could do ourselves a great service by doing automated testing of random configurations as part of CI. We could also do fault injection if this works out well.

Parameters that would vary:

  • DAG size and shape
  • Anonymous and named function thunks
  • Thunk/Scheduler options
  • Processor types (ThreadProc for now)
  • Checkpointing
  • Dynamic DAG extension and querying
  • SIGINT handling

Some metrics we'd want to test:

  • Correctness
  • Total runtime length
  • Per-process memory usage
  • Caching statistics
  • Network transfer statistics
  • Visualization output

Contributor guide

Tech stack
None
Domain
testingbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
clear
Prerequisites
Julia languageDagger.jl internalsTesting conceptsCI/CD basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue proposes a chaos testing framework for Dagger.jl. Begin by exploring the existing test suite in the 'test' directory and understanding the scheduler architecture in 'src/scheduler.jl'. Implement a random configuration generator covering the listed parameters and integrate with CI via GitHub Actions. Measure correctness, runtime, memory, and other metrics as specified.