[This article was first published on Akhila Chowdary, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Over the past few months, I have been working on testing the Rcpp packages using RcppDeepState in the cluster. When we fuzz test each Rcpp function-specific testharness I have found issues in 137 packages.
The List of packages that we found issues in can be found (here)[https://akhikolla.github.io/package-specific/root.html].
The number of inputs passed onto the target binary keeps varying depending on the clock speed, number of cores, cache size of the system. The default timer is 2 minutes, depending on the system’s speed RcppDeepState generates as many inputs as possible. The inputs generated are usually stored in .crash/.fail/.pass files.
To leave a comment for the author, please follow the link and comment on their blog: Akhila Chowdary.
R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.