Peter Firmstone wrote:
...
I think that after stepping throught these tests many times, that the
only reason this test even passes is the bogus config file isn't found
perhaps this is related to file url or something. I don't fully
understand the bug the test is looking for. Any ideas.
Did you see that the latest Hudson test ran clean?
My intuition is that this is that the 1.5 v.s 1.6 difference may be
related to libraries looking in different places for files. The
variation among 1.6 runs is more likely to be related to left over state
from previous runs.
This subdivides into two theories:
1. There is a bug in River itself that should be detected by the test,
but the test falsely passes if there is some left over state from a
previous run of the test suite.
2. River is fine, and the tests should pass, but some left over, for
example from failure of a different test on a previous QA run, prevents
it from succeeding.
I would not worry too much about what the test is looking for. That may
or may not be what it is finding.
Patricia
