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
Copy file name to clipboardExpand all lines: cran-comments.Rmd
+7-9Lines changed: 7 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,11 @@ title: "cran-comments"
3
3
output: github_document
4
4
---
5
5
6
+
## Resubmission 5 to CRAN
7
+
8
+
* Repairs a broken link in `vignettes/mainfunctions.Rmd`
9
+
10
+
6
11
## Resubmission 4 to CRAN
7
12
8
13
* Wrap example section of `predict()` and `brokenstick()` in `\donttest{}` to reduce CPU time
@@ -48,7 +53,7 @@ Status: OK
48
53
`devtools::check_win_devel()` resulted in:
49
54
50
55
```
51
-
Note: CPU time > 10s for predict example section
56
+
OK
52
57
```
53
58
54
59
### RHUB
@@ -60,16 +65,9 @@ rhub::check_for_cran()
60
65
`rhub::check_for_cran()` produces "SUCCESS" (three times) and one note:
61
66
62
67
```
63
-
* checking examples ... NOTE
64
-
Examples with CPU (user + system) or elapsed time > 5s
65
-
user system elapsed
66
-
predict 7.44 0.02 7.48
67
-
brokenstick 4.96 0.02 5.15
68
+
Success
68
69
```
69
70
70
-
Comment:
71
-
Slightly above the threshold of 5 seconds. Both example sections demonstrate many capabilities of these functions to the end user. For clarity, I think these examples should remain as they are.
0 commit comments