Raphael 'kena' Poss

- the stdout/stderr of actions should be reported on the screen, this is important especially for long-running actions - ditto exit code

For example ``` parameter foo is 123 role :foo echo $foo end ``` related to #4

1. it would be nice if the parameters set by the config could get their defaults from env vars 2. the value of all env vars used by a config...

For reproducibility it's important to collect build info. This probably needs two things: - syntax extension to list involved programs/binaries - collect the data in the report

If the spotlight fails, this is a hard error that should stop the test. Currently the test proceeds and no final error is reported.

Once the CSV files are collected and `result.json` provides all the details, it should be possible to re-plot. This is useful to refine the output after a multi-hour test has...

Support sqlite builds with DQS=off

7

If sqlite3 is built with double-quoted string literals disabled (which is recommended, see https://www.sqlite.org/compile.html#dqs), diskcache starts failing with the following crypting error: ``` no such column: "size" ``` This is...

feature request: custom column alignments

2

Currently anything that _starts_ with a number is padded left and thus right-aligned. This causes irregular output when a column containing strings happens to contain a string starting with decimal...

[WIP] Create a framework to exercise the `go test` output

8

Prior to this patch, there was no way to exercise the behavior of `-rewrite` nor how errors and sub-tests would be reported in the output of `go test -v`. This...

Stop relying on `pkg/errors` to handle stack traces

7

Today the stack trace formatting code delegates to `pkg/errors/stack.go`. However, that code uses `runtime.FuncForPC` and emits file paths in the stack trace derived from the raw file name of the...