Heikki Toivonen wrote:
Functional test output is totally under our control, and switched to the
new cats format pretty recently. Unfortunately it outputs many lines
that get recognized by the Tbox log parser as error lines even though
they are not errors.
My comments were focused on the functional test output; it's this output
that's so hard to deal with now, because (a) it's not integrated with
the chandler.log output, and (b) the tinderbox error parser is doing
such a bad job of producing an index from its output.
Performance tests can fail as well; these are transitioning to new cats
at some point as well.
Finally there is a lot of output we don't really have much control over,
which comes from make, compiler, etc.
The parser we use is the generic 'unix error parser' that comes with
Tinderbox. I don't know how difficult it would be to change that. In
fact, I'd rather not change it unless absolutely necessary, because
maintaining a hacked tbox is not fun.
I've made a few modifications to the error parser in the past to help it
do a better job on the (pre-cats) output, so it's not like it's out of
our control to do so -- it's a much better investment of our time to
merge new versions of the error parser when we infrequently upgrade the
tbox, versus us looking for useful information in a giant log every time
a failure happens.
...Bryan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
