search for: verify_output

...C/C++ breakpoint" > > HTH! Yes, that looks like it would pin down the location of the problem. Here's some sample output from it: Running ?testthat.R? [41s/42s] Running the tests in ?tests/testthat.R? failed. Last 13 lines of output: Start test: can use constructed calls in verify_output() (#945) 'test-verify-output.R:55' [success] End test: can use constructed calls in verify_output() (#945) Start test: verify_output() doesn't use cli unicode by default 'test-verify-output.R:65' [success] 'test-verify-output.R:73' [success] End...

...C/C++ breakpoint" > > HTH! Yes, that looks like it would pin down the location of the problem. Here's some sample output from it: Running ?testthat.R? [41s/42s] Running the tests in ?tests/testthat.R? failed. Last 13 lines of output: Start test: can use constructed calls in verify_output() (#945) 'test-verify-output.R:55' [success] End test: can use constructed calls in verify_output() (#945) Start test: verify_output() doesn't use cli unicode by default 'test-verify-output.R:65' [success] 'test-verify-output.R:73' [success] End...

...t; > Yes, that looks like it would pin down the location of the problem. > Here's some sample output from it: > > Running ?testthat.R? [41s/42s] > Running the tests in ?tests/testthat.R? failed. > Last 13 lines of output: > Start test: can use constructed calls in verify_output() (#945) > 'test-verify-output.R:55' [success] > End test: can use constructed calls in verify_output() (#945) > > Start test: verify_output() doesn't use cli unicode by default > 'test-verify-output.R:65' [success] > 'test-verify...

Am 10.01.23 um 21:28 schrieb Duncan Murdoch: > 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