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
Action's comments #6
Conversation
No error has been reported by RcppDeepState Analyzed functions summary
|
In the last few commits I've made improvements to the case where RcppDeepState finds no errors. I've temporarily turned off the workflow that tests testSAN in favor of checking TestPackage, a package that is known to be error-free. As can be seen from the most recent gtihub-actions comment, a table showing the summary of each examined function with the number of tests run has been included with the message "No error has been reported by RcppDeepState". |
@tdhock In this pull request I also managed to add a third option for the comment argument. There are three choices:
This has been tested in the last action execution triggered by the commit f7c351c. The action has been run on the bug-free package with the comment parameter set to |
To recap the changes made in this pull request, I implemented the following features:
|
that "Analyzed functions summary" looks good! |
RcppDeepState Report
|
@tdhock I changed the action such that it adds the comment once in a pull request and updates it in subsequent runs. Running twice the action on the testSAN package allowed me to test this functionality. The final comment illustrates the result: the comment has been created on the first run of job and then updated on the second run. |
I noticed that although the |
@tdhock Does it make sense to include the "Analyzed functions summary" even if RcppDeepState discovers errors? For now that summary is printed only in the case RcppDeepState finds no error. |
This pull request aims to enhance the action's commenting system.