e25b4aeea0
Please add all kinds of weird ideas, nice-to-haves, or inconveniences (with or without suggestions on how to deal with them) you experience when using Fail*. git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1600 8c4709b5-6ec9-48aa-a5cd-a96041d1645a
13 lines
550 B
Plaintext
13 lines
550 B
Plaintext
This file documents ideas/wishes especially from a Fail* *user* perspective.
|
|
|
|
- Recurring Fail* API usage patterns in experiment/campaign implementations
|
|
(that could be implemented in a reusable way, e.g. in a library that sits
|
|
between the Fail* API and the experiment)
|
|
* Fault-space pruning (FIXME elaborate)
|
|
* Preparation vs. final experiment steps -> cmake-driven, automatically
|
|
build 2 fail-client binaries? (FIXME elaborate)
|
|
* ...
|
|
|
|
- Campaign distribution: More foolproof host CPU load/local users/RAM usage
|
|
examination
|