>>>>> Dirk Eddelbuettel writes:
Thanks. So I guess we should publish the new RcppArmadillo and ask the
quanteda maintainer to fix as necessary?
Best
-k
> Hi Kurt,
> Much appreciate the update.
> On 16 August 2017 at 17:23, Kurt Hornik wrote:
> | >>>>> Dirk Eddelbuettel writes:
> |
> | Dirk:
> |
> | When checking the reverse depends, we're seeing problems with quanteda,
> | both with the old version of this as well as the new one published last
> | night. E.g.
> |
> | Package: quanteda [Old version: 0.9.9-65, New version: 0.99]
> | Check: examples
> | New result: ERROR
> | Running examples in ‘quanteda-Ex.R’ failed
> | The error most likely occurred in:
> |
> | > base::assign(".ptime", proc.time(), pos = "CheckExEnv")
> | > ### Name: textmodel_wordfish
> | > ### Title: wordfish text model
> | > ### Aliases: textmodel_wordfish
> | >
> | > ### ** Examples
> | >
> | > textmodel_wordfish(data_dfm_lbgexample, dir = c(1,5))
> | Error in wordfishcpp_mt(x, as.integer(dir), 1/(priors^2), tol, disp,
> dispersion_floor, :
> | dfmSparse is not supported.
> | Calls: textmodel_wordfish -> textmodel_wordfish.dfm -> wordfishcpp_mt ->
> .Call
> | Execution halted
> |
> | and in fact all problems seem to have the "dfmSparse is not supported."
> | errors. Are you seeing these too? Should we contact the quanteda
> | maintainer about this?
> I have been seeing _fairly consistent_ failures for quanteda with both Rcpp
> and RcppArmadillo for quite some time. You can see more details at the usual
> rcpp-logs repo.
> As such, I have ignored its most recent failure with RcppArmadillo
> 0.7.960.1.0. The last (of several) reverse depends logs preceding the upload
> has its summary here:
> https://github.com/RcppCore/rcpp-logs/blob/master/results/rcpparmadillo/RcppArmadillo-Summary-20170810.txt
> As you can see: 372 passed, 3 failed and 2 were skipped by my choice.
> On occassion, I dive into packages that fail, ie Rob's "forecast" apparently
> only failed for me but not elsewhere. As it was reproducible, Rob and I
> agreed on a change he made. So it no longer fails for me either.
> Similarly, preceding the currently-pending upload of a new BH I have reached
> out to two packages one of which was already updated, the other is pending.
> But I don't have the bandwidth to chase all failures for all packages, and
> some are too persistent. And that is why I uploaded RcppArmadillo last Friday.
> Dirk
> | Best
> | -k
> |
> |
> | > RcppArmadillo 0.7.960.1.0 has been ready for a few days and sitting at
> CRAN,
> | > due to a seemingly unlucky combination of travel, weekend,, systems outage
> | > and what not. But it has been five full days now , and nobody has told me
> | > what if anything is non-standard with the package so ... I give up now.
> |
> | > So it is as of now also in the drat repo for the RcppCore org, so just see
> | > the README.md at
> | > https://github.com/RcppCore/drat
> | > which has the following example which is applicable:
> |
> | > # first add the repo
> | > drat:::add("RcppCore")
> | > # either install just one or more given packages
> | > install.packages("RcppArmadillo")
> | > # or update already installed packages
> | > update.packages()
> |
> | > You can also add the repo URL by hand to options("repos"), or supply it to
> | > install.packages(), or ... I happen to like drat.
> |
> | > The files NEWS.Rd and ChangeLog have the goods, I make a fuller
> announcement
> | > if and when it makes it to CRAN.
> |
> | > This release features a lot of excellent Google Summer of Code work by
> | > Binxiang Ni. Again, more about that if and when we get to make a true
> | > release announcement.
> |
> | > Dirk
> |
> | > --
> | > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
> |
> --
> http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
