 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
32 messages in org.perl.cpan-testers-discussRe: revokable FAIL (was Reporting Bug...| From | Sent On | Attachments |
|---|---|---|
| David Golden | Sep 3, 2008 2:09 pm | |
| Andrew Moore | Sep 3, 2008 2:28 pm | |
| David Cantrell | Sep 4, 2008 6:39 am | |
| David Cantrell | Sep 4, 2008 6:42 am | |
| David Golden | Sep 4, 2008 7:28 am | |
| Gabor Szabo | Sep 4, 2008 7:35 am | |
| Greg Sabino Mullane | Sep 4, 2008 8:29 am | |
| Andy Lester | Sep 4, 2008 8:41 am | |
| chromatic | Sep 4, 2008 10:08 am | |
| Greg Sabino Mullane | Sep 4, 2008 11:19 am | |
| David Golden | Sep 4, 2008 11:30 am | |
| Steffen Schwigon | Sep 4, 2008 11:42 am | |
| Andy Lester | Sep 4, 2008 11:52 am | |
| Andrew Moore | Sep 4, 2008 12:11 pm | |
| Andy Lester | Sep 4, 2008 12:21 pm | |
| Andrew Moore | Sep 4, 2008 12:29 pm | |
| Barbie | Sep 4, 2008 1:13 pm | |
| Bram | Sep 4, 2008 1:13 pm | |
| David Golden | Sep 4, 2008 1:56 pm | |
| Eric Wilhelm | Sep 4, 2008 2:16 pm | |
| David E. Wheeler | Sep 5, 2008 8:48 am | |
| David E. Wheeler | Sep 5, 2008 9:07 am | |
| Andy Lester | Sep 5, 2008 9:13 am | |
| David E. Wheeler | Sep 5, 2008 9:17 am | |
| chromatic | Sep 5, 2008 10:31 am | |
| David E. Wheeler | Sep 5, 2008 11:22 am | |
| chromatic | Sep 5, 2008 11:35 am | |
| David E. Wheeler | Sep 5, 2008 11:45 am | |
| Eric Wilhelm | Sep 5, 2008 11:55 am | |
| Eric Wilhelm | Sep 5, 2008 2:48 pm | |
| David Golden | Sep 5, 2008 3:22 pm | |
| Eric Wilhelm | Sep 5, 2008 4:41 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: revokable FAIL (was Reporting Bugs Where ... (was ...)) | Actions... |
|---|---|---|
| From: | David Golden (xda...@gmail.com) | |
| Date: | Sep 5, 2008 3:22:33 pm | |
| List: | org.perl.cpan-testers-discuss | |
On Fri, Sep 5, 2008 at 5:48 PM, Eric Wilhelm <scra...@gmail.com> wrote:
So, whether a 2.0 design consideration or whatever, please help me get the things I don't have to remember out of my brain and into the computer. And maybe I'll even be able to help keep other authors from scratching their head wondering what happened.
It's on the list. 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.)
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, we'd need reports to bundle up testers CPAN/CPANPLUS/CPAN::Reporter/YACSmoke/etc configuration files and so on. Benefit probably not worth the cost, hassle and privacy concerns. Most of the obvious problem "Build -j3" can probably be caught with a regex.
And now, feature creep: optional notifications of "please disregard these reports: ... " for affected authors who have just started ambitiously scratching their heads at the time the issue is identified. ;-)
When we have 2.0 up and running, patches will be welcome. ;-)
-- David