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

figure out what to do with forceZeroCoverage feature that does not work anymore in batch side #909

Closed
jmecosta opened this issue Jul 7, 2016 · 3 comments · Fixed by #1007
Assignees
Labels
Milestone

Comments

@jmecosta
Copy link
Member

jmecosta commented Jul 7, 2016

  • drop?
  • or move to server side.
@jmecosta jmecosta mentioned this issue Jul 7, 2016
@guwirth guwirth added this to the 0.9.7 milestone Jul 7, 2016
@guwirth
Copy link
Collaborator

guwirth commented Jul 7, 2016

Found this. Seems to work different now.

@jmecosta
Copy link
Member Author

jmecosta commented Jul 7, 2016

Cool thanks, that will do and we should be dropping the force coverage to
zero. If I understood properly even the bullseye model should work properly

On Thu, 7 Jul 2016 19:37 Günter Wirth, [email protected] wrote:

Found this. Seems to work different now.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#909 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA_jyJMdFC_OEtH3QVYA-N_xA45h5F_Aks5qTStWgaJpZM4JG4Hn
.

@guwirth
Copy link
Collaborator

guwirth commented Oct 24, 2016

Did some first tests over the weekend and get different coverage numbers (e.g. 19% coverage instead 5% before). Seems forceZeroCoverage is still needed. Will create a call in the SQ forum to ask why MMF-166 is not working.

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

Successfully merging a pull request may close this issue.

2 participants