В Sun, 13 Aug 2023 00:59:40 -0700
Michael Topper пишет:
>- Setting the nthreads argument to 2 in fixest::feels() in case
> this is the problem as suggested.
Any chance you could be hitting some other code paths in the fixest
package while working on the objects returned by fixest::feols()?
I have tried the following:
- Trimming down the examples substantially to only run 1 regression
per-function.
- Setting the nthreads argument to 2 in fixest::feels() in case this is
the problem as suggested.
- Tried to use skip_cran_test() on the tests that include fixest
regress
On 13.08.2023 08:14, Ivan Krylov wrote:
В Sat, 12 Aug 2023 22:49:01 -0700
Michael Topper пишет:
It appears that some of my examples/tests are taking too
long to run for CRAN's standards.
I don't think they are running too long; I think they are too parallel.
The elapsed time is below 1s,
В Sat, 12 Aug 2023 22:49:01 -0700
Michael Topper пишет:
> It appears that some of my examples/tests are taking too
> long to run for CRAN's standards.
I don't think they are running too long; I think they are too parallel.
The elapsed time is below 1s, but the "user" time (CPU time spent in
the
Hello all,
Not sure how to handle this, as it had not been an issue on my previous
CRAN submissions. It appears that some of my examples/tests are taking too
long to run for CRAN's standards. Is there a way around this other than the
simple "change the example" or "change the test"?
Moreover, is
