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

error saving Result does *not* cause Report to be skipped #1

Closed
sheppard opened this issue Nov 6, 2014 · 1 comment · Fixed by #5
Closed

error saving Result does *not* cause Report to be skipped #1

sheppard opened this issue Nov 6, 2014 · 1 comment · Fixed by #5
Milestone

Comments

@sheppard
Copy link
Member

sheppard commented Nov 6, 2014

But it is reported as skipped to the user. This results in orphaned reports that are not related to the IOModel.

@sheppard
Copy link
Member Author

sheppard commented Apr 8, 2016

Also, make sure result.empty is set in this case (or is that a vera bug?)

sheppard added a commit that referenced this issue May 12, 2017
sheppard added a commit that referenced this issue May 12, 2017
@sheppard sheppard added this to the 1.0 milestone Feb 5, 2020
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

Successfully merging a pull request may close this issue.

1 participant