You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the most recent commits, I added a third column to the summary table, which shows the number of tests that detected at least one error within the tested package.
In addition, I modified all of the column names to remove the underscore character between words.
In this comment, I'm referring to the errors column inside the table beneath the Analyzed functions summary paragraph as the "third" column. Here is the summary table I am referring to:
function name
tested inputs
errors
rcpp_read_out_of_bound
3
3
rcpp_use_after_deallocate
3
3
rcpp_use_after_free
3
3
rcpp_use_uninitialized
3
0
rcpp_write_index_outofbound
3
3
rcpp_zero_sized_array
3
3
In the above table we can see that all the functions except rcpp_use_uninitialized have been analyzed and an error has been detected for each test. rcpp_use_uninitialized was analyzed three times but no error was reported (errors column set to 0).
right, that makes sense and looks good overall.
you wrote that this number is "the number of tests that detected at least one error within the tested package" but I think it would be more accurate to say it is, for each function, the number of inputs which caused at least one valgrind message/issue, right?
the column name "errors" may therefore be misleading -- maybe change to "inputs with issues" or similar?
for each function, the number of inputs which caused at least one valgrind message/issue, right?
Yes you are right, this is more accurate
maybe change to "inputs with issues" or similar?
This is better; the keyword errors is misleading. I didn't want to give that column a complicated name, but I believe it is better to explain that it corresponds to the total number of inputs that created at least one problem.
This is fantastic; thank you for including the binsegRcpp RcppDeepState report in this pull request.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request implements the SHA reference that was discussed in the issue #13. These changes amount to:
file_lineandaddress_tracecolumns to the commit SHA rather than the pull request.This PR also provides the following feature:
Report detailsparagraph.Fixes #13