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

Masking expected failures #10

Closed
ajdlinux opened this issue Apr 6, 2016 · 1 comment
Closed

Masking expected failures #10

ajdlinux opened this issue Apr 6, 2016 · 1 comment

Comments

@ajdlinux
Copy link
Collaborator

ajdlinux commented Apr 6, 2016

As per discussion with mpe, longer term we need to look at ways for masking expected failures.
Some options:

  • Know the state of the base branch, only report failures which have been introduced specifically by the new patch
  • Allow maintainer to specify certain jobs/configs etc that will not be reported as failures
@ajdlinux
Copy link
Collaborator Author

ajdlinux commented Apr 6, 2016

@ruscur: "Maybe this is something that should be at the Jenkins level. If we can tag jobs as "dev" or "stable", we can compare the "dev" thing we just started building to the latest "stable" run and return a result from there accordingly.

This is something we need to address but it's very difficult and won't be for some time, I feel."

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

No branches or pull requests

2 participants