Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark incoming reports with failed dependencies as INVALID #25

Open
preaction opened this issue Aug 3, 2018 · 0 comments
Open

Mark incoming reports with failed dependencies as INVALID #25

preaction opened this issue Aug 3, 2018 · 0 comments

Comments

@preaction
Copy link
Member

There are often incoming reports that are clearly not good-faith effort to test the distribution: A misconfigured reporter, an accidental "Yes" answer to the question "Prereqs failed to install, try to continue anyway?", or other things.

There are some ways that a test report will warn about these things:

When we find one of these things, we should process the report in a different way:

  • If the report is a pass, it means that either the distribution dependencies can be relaxed, or the distribution's tests do not cover the cases where the dependency is needed.
    • We can add a note to the report explaining this
    • We could grade the report as INVALID or UNKNOWN or even FAIL
  • If the report is a fail, it means nothing: The distribution said it required libraries that are not present
    • Grade the report as INVALID

If we are changing the report given to us by the reporter, we need to record the changes so we can track down issues with reporters in the future. See cpan-testers/cpantesters-schema#31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant