"Github" -> "Git"
-N
On 6/2/25 9:15 AM, Balasubramanian Narasimhan wrote:
While on the subject, one useful workflow I have adopted (e.g. package
cubature) is to clone the underlying C library to a Github repo.
(Always happy to hear of others!)
Then create a branch called `R_pkg` and make cha
While on the subject, one useful workflow I have adopted (e.g. package
cubature) is to clone the underlying C library to a Github repo. (Always
happy to hear of others!)
Then create a branch called `R_pkg` and make changes on this branch and
use it as the source for your C library. Not only do
My revision of package 'secr' fails CRAN pre-test on Windows (R 4.5.0) because
total check time exceeds 10 min (it's 760 seconds or 13 min). I can't see how
to fix this as none of the times listed in the log
https://win-builder.r-project.org/incoming_pretest/secr_5.2.2_20250602_054847/Windows/00
On 3 June 2025 at 00:12, Murray Efford via R-package-devel wrote:
| My revision of package 'secr' fails CRAN pre-test on Windows (R 4.5.0)
because total check time exceeds 10 min (it's 760 seconds or 13 min). I can't
see how to fix this as none of the times listed in the log
https://win-builde
On the face of it, I would need to throw out all the examples, and all the
tests. That can't be right. Am I wrong to take the times in the log at face
value? Where did the other 6 minutes go? Please excuse my obtuseness.
From: Dirk Eddelbuettel
Sent: Tuesday, 3
That log ends with status OK, so is that the run that had the problem?
Isn't that time exceeded message in the log somewhere?
On Tue, 3 Jun 2025 at 11:41, Murray Efford via R-package-devel <
r-package-devel@r-project.org> wrote:
> On the face of it, I would need to throw out all the examples, an
Yes, that run is the problem. There is an attachment from CRAN-pretest with
this NOTE that I take to be the issue:
Flavor: r-devel-windows-x86_64
Check: *, Result: NA
Flavor: r-devel-windows-x86_64
Check: Overall checktime, Result: NOTE
Overall checktime 13 min > 10 min
Flavor: r-devel-linux-x8
