search for: locationreporter

...ck('rlibkriging', reporter = "progress") > > should at least show you the tests that finished running before the > timeout. I had similar problems with testthat and timeouts when mass-checking packages on patched R versions. My notes say > ## testthat's 'LocationReporter' does cat() after each expectation > ## so we can see results even if timeout is reached > options(testthat.default_check_reporter = c("Location", "Check")) The help("LocationReporter") says: "This reporter simply prints the location of every expectati...

...ter = "progress") >> >> should at least show you the tests that finished running before the >> timeout. > > I had similar problems with testthat and timeouts when mass-checking > packages on patched R versions. My notes say > >> ## testthat's 'LocationReporter' does cat() after each expectation >> ## so we can see results even if timeout is reached >> options(testthat.default_check_reporter = c("Location", "Check")) > > The help("LocationReporter") says: "This reporter simply prints the > locat...

...r = "progress") >> >> should at least show you the tests that finished running before the >> timeout. > > I had similar problems with testthat and timeouts when mass-checking > packages on patched R versions. My notes say > >> ## testthat's 'LocationReporter' does cat() after each expectation ## >> so we can see results even if timeout is reached >> options(testthat.default_check_reporter = c("Location", "Check")) > > The help("LocationReporter") says: "This reporter simply prints the > lo...

...t;>> >>> should at least show you the tests that finished running before the >>> timeout. >> >> I had similar problems with testthat and timeouts when mass-checking >> packages on patched R versions. My notes say >> >>> ## testthat's 'LocationReporter' does cat() after each expectation ## >>> so we can see results even if timeout is reached >>> options(testthat.default_check_reporter = c("Location", "Check")) >> >> The help("LocationReporter") says: "This reporter simply prints...

On 10/01/2023 2:05 p.m., Ivan Krylov wrote: > On Tue, 10 Jan 2023 16:27:53 +0000 > RICHET Yann <yann.richet at irsn.fr> wrote: > >> In facts, 10 threads are asked by armadillo for some LinAlg, which >> backs to two threads as warned. > > I think you're right about your tests de-facto using two threads, but > it might be a good idea to _default_ to up to