Re: [R-pkg-devel] Check time > 10min

2025-06-04 Thread Ivan Krylov via R-package-devel
On Tue, 3 Jun 2025 15:36:09 +0200 Sebastian Meyer wrote: > It is indeed unfortunate and perhaps a bug that the Windows check log > shows no runtime for > > > * checking whether package 'secr' can be installed ... OK > > (which on the Debian check machine was reported with 164s) On the same

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Joshua Ulrich
2025 02:33 > To: Greg Hunt > Cc: Dirk Eddelbuettel ; Murray Efford > ; R Package Development > > Subject: Re: [R-pkg-devel] Check time > 10min > > > Greg, > > On 4 June 2025 at 00:19, Greg Hunt wrote: > | In the original email, there was this: > | > | * ch

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Murray Efford via R-package-devel
From: Dirk Eddelbuettel Sent: Wednesday, 4 June 2025 02:33 To: Greg Hunt Cc: Dirk Eddelbuettel ; Murray Efford ; R Package Development Subject: Re: [R-pkg-devel] Check time > 10min Greg, On 4 June 2025 at 00:19, Greg Hunt wrote: | In the original email, there was t

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Dirk Eddelbuettel
Greg, On 4 June 2025 at 00:19, Greg Hunt wrote: | In the original email, there was this: | | * checking examples ... [87s] OK | * checking tests ... [59s] OK | | Am I interpreting it wrong or are these numbers the elapsed times for checking | examples and tests?   If you follow the URL from t

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Greg Hunt
Dirk, In the original email, there was this: * checking examples ... [87s] OK * checking tests ... [59s] OK Am I interpreting it wrong or are these numbers the elapsed times for checking examples and tests? Greg On Wed, 4 Jun 2025 at 00:17, Dirk Eddelbuettel wrote: > > Greg, > > On 3 June 202

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Dirk Eddelbuettel
Greg, On 3 June 2025 at 23:58, Greg Hunt wrote: | To clarify the reference to zero cost.   | | If Murray is being told that total time is thirteen minutes and that the time | needs to be less than ten, he might try to reduce the cost of tests and | examples, but they don't in total add up to th

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Dirk Eddelbuettel
On 3 June 2025 at 15:36, Sebastian Meyer wrote: | Am 03.06.25 um 13:22 schrieb Greg Hunt: | > Dirk, | > Even if he gets the test and example times to zero, his total time in that | > thirteen minute run is still above ten minutes. In my view the incomplete | > time reporting (we don't know what

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Greg Hunt
Dirk, To clarify the reference to zero cost. If Murray is being told that total time is thirteen minutes and that the time needs to be less than ten, he might try to reduce the cost of tests and examples, but they don't in total add up to the required three minutes. Even if the combined cost of te

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Sebastian Meyer
Am 03.06.25 um 13:22 schrieb Greg Hunt: Dirk, Even if he gets the test and example times to zero, his total time in that thirteen minute run is still above ten minutes. In my view the incomplete time reporting (we don't know what makes up the thirteen minutes) is a bug in the build process. It

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Dirk Eddelbuettel
Greg, On 3 June 2025 at 21:22, Greg Hunt wrote: | Dirk, | Even if he gets the test and example times to zero, his total time in that | thirteen minute run is still above ten minutes.  In my view the incomplete time | reporting (we don't know what makes up the thirteen minutes) is a bug in the |

Re: [R-pkg-devel] Check time > 10min

2025-06-03 Thread Greg Hunt
Dirk, Even if he gets the test and example times to zero, his total time in that thirteen minute run is still above ten minutes. In my view the incomplete time reporting (we don't know what makes up the thirteen minutes) is a bug in the build process. Greg On Tue, 3 Jun 2025 at 10:54, Dirk Eddel

Re: [R-pkg-devel] Check time > 10min

2025-06-02 Thread Murray Efford via R-package-devel
nux-x86_64-debian-gcc Check: *, Result: OK From: Greg Hunt Sent: Tuesday, 3 June 2025 13:45 To: Murray Efford Cc: Dirk Eddelbuettel ; R Package Development Subject: Re: [R-pkg-devel] Check time > 10min That log ends with status OK, so is that the run that h

Re: [R-pkg-devel] Check time > 10min

2025-06-02 Thread Greg Hunt
t; To: Murray Efford > Cc: R Package Development > Subject: Re: [R-pkg-devel] Check time > 10min > > > 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 tim

Re: [R-pkg-devel] Check time > 10min

2025-06-02 Thread Murray Efford via R-package-devel
ay, 3 June 2025 12:54 To: Murray Efford Cc: R Package Development Subject: Re: [R-pkg-devel] Check time > 10min 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 exceed

Re: [R-pkg-devel] Check time > 10min

2025-06-02 Thread Dirk Eddelbuettel
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

[R-pkg-devel] Check time > 10min

2025-06-02 Thread Murray Efford via R-package-devel
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