Relatively long-running tests for handling large amounts of data, numerous iterations, etc. May have some NUnit, but probably less pervasive than the smaller unit tests.
Couple that with getting runtime performance figures. Think knitr and R Markdown, perhaps.
* Impact of using the lock mechanism on preserve/unpreserve. Guidelines
* Character vectors: measure, and advise best practices.
* Figures on Linux and Mono
Comments: Here's a good example. From pp71 of the DAAG manual, I manually ran this plot: library(DAAG) plot(northing ~ easting, data=frogs, pch=c(1,16)[frogs$pres.abs+1], xlab="Meters east of reference point", ylab="Meters north"); Submitting this code to the service several times in a row yielded : "Unable to Retrieve an R error message. Evaluating 'geterrmessage()' fails. The R engine is not in a working statement" each time Changing the pch char to pch=2 returned the plot and a "C stack usage 32054504 is too close to the limit" error with the correct plot. Changing the pch line back produced the correct plot on the next try. Then I started getting the geterrmessage()" failure again. See the attached image for a composted view of the two cases. I'm adding some tracing around the R object pinning code to see if it yields anything fruitful.
Couple that with getting runtime performance figures. Think knitr and R Markdown, perhaps.
* Impact of using the lock mechanism on preserve/unpreserve. Guidelines
* Character vectors: measure, and advise best practices.
* Figures on Linux and Mono
Comments: Here's a good example. From pp71 of the DAAG manual, I manually ran this plot: library(DAAG) plot(northing ~ easting, data=frogs, pch=c(1,16)[frogs$pres.abs+1], xlab="Meters east of reference point", ylab="Meters north"); Submitting this code to the service several times in a row yielded : "Unable to Retrieve an R error message. Evaluating 'geterrmessage()' fails. The R engine is not in a working statement" each time Changing the pch char to pch=2 returned the plot and a "C stack usage 32054504 is too close to the limit" error with the correct plot. Changing the pch line back produced the correct plot on the next try. Then I started getting the geterrmessage()" failure again. See the attached image for a composted view of the two cases. I'm adding some tracing around the R object pinning code to see if it yields anything fruitful.