Fork me on GitHub
Braden Shepherdson16:11:34

I find myself getting a handful of errors, say 4 or 5, but with 200-line stack traces. I want to see the stacks so I can figure out what's wrong, but I'm also finding it tedious to page up a dozen times or more to find the topmost failure of the most recent run.

Braden Shepherdson16:11:56

has there been any thought given to a web reporter or other more navigable form of output?