# from David Golden
# on Friday 05 September 2008 15:22:
>On Fri, Sep 5, 2008 at 5:48 PM, Eric Wilhelm wrote:
>The one thing that concerns me is that some authors
>object to FAIL reports showing up on their search.cpan.org page and
>will just want them all blanked out.
>
>So my thought at the moment is that we let people "dispute" reports --
>or some synonym -- and let people filter them if they don't want to
>see them. (Authors or end users.)
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.
>> Is there a machine/configuration identifier of some sort and/or
>> other ways to characterize a "report source" such that once the
>> cause of a false report is identified every report caused by that
>> same issue could be automatically crossed off?
>
>Yes and no. "Modern" reports have toolchain info, environment info,
>etc. But to be really complete, ... configuration files ... cost,
>hassle and privacy concerns. ... "Build -j3" ... caught with a regex.
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
--
"It ain't those parts of the Bible that I can't understand that
bother me, it's the parts that I do understand."
--Mark Twain
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
