On Thu, 7 Dec 2023 12:22:11 -0500
Andrew Robbins wrote:
> I just benchmarked devtools::check() (which is actually a build
> followed by a check) on my Ryzen 5700X/intel 660p system with a bunch
> of stuff going on in the background and got just over 11 minutes. I
> don't actually think its
Hi again,
I just double checked the test invocations of INMF which are on /much/
larger matrices with /far/ more iterations and am still seeing zero
seconds. That /is/ a bug, but its not a related one. The objective error
of 44244.4 is what it should be returning for the example matrices.
On Tue, 5 Dec 2023 17:16:37 -0500
Andrew Robbins via R-package-devel
wrote:
> Every time, it reports a runtime of zero seconds for INMF res1
I get exactly 0 seconds for both res1 and res2 on both my Windows
machines and on my Linux machine. I had discounted that as an integer
type used
I spent this afternoon trying to figure out what exactly was going on
here. In my several submissions to winbuilder (sorry Uwe) I have
confirmed that the culprit is /not/:
* writing to Rcpp::rcout
* openmp
* std::chrono::high_resolution_clock
Every time, it reports a runtime of zero
Hi Ivan,
Thank you for giving my package check a run-through. You have it
correct-every win-builder log hangs/halts in that exact example. The
only other anomaly I notice on win-builder is that the elapsed time
reported to Rcout is 0-which is clearly incorrect. DNDEBUG removing the
assert
Hi Andrew Robbins,
В Mon, 27 Nov 2023 12:22:44 -0500
Andrew Robbins via R-package-devel
пишет:
> I'm currently attempting to submit a package to CRAN and am getting
> timeouts during the "running examples" phase of the winbuilder tests
> that I cannot reproduce locally or on the r-hub windows
Hi All,
I'm currently attempting to submit a package to CRAN and am getting
timeouts during the "running examples" phase of the winbuilder tests
that I cannot reproduce locally or on the r-hub windows runner. How do I
go about debugging this?
Winbuilder results linked here:
