# from David Golden # on Friday 05 September 2008 15:22:

This goes back to the default presentation issue and the fact that we only have one presentation at the moment, but this particular case is more one of absolutes and not preferences. We are absolutely sure that the bug elsewhere is not a FAIL and not just something to be disputed.

That is, I see it as an attribute of the report(s). Maybe that can be elegantly handled in the presentation layer or whatever, but I would tend to e.g. change the label to "SPLAT" so that it doesn't get easily mis-presented as FAIL by a webservices consumer, etc.

So... no identifier? Perhaps the regex works but knowing more about the test environment (strip the paths from the config?) would be useful. If nothing else, perhaps take all the config data and md5 hash it so you can at least track the "report source" in the database. I would think "no big deal" if that hash changes occasionally or whatever. I'm just trying to suggest how a runaway bot/bug/config could be easily tracked down (and trying to account for the case of more than one setup on a single machine.)

Thanks, Eric

--------------------------------------------------- http://scratchcomputing.com