similar to: round(x, dig) [was "Development version of R fails tests .."]

>>>>> Hugh Parsonage >>>>> on Sat, 8 Feb 2020 21:12:43 +1100 writes: > The only observation I can make is that the change to > round() was made in r77727 whereas your R-devel appears to > be r77715 (so would not exhibit the fixed behaviour). My > guess is that there was a perpetual installation failure > after r77715 but that

The only observation I can make is that the change to round() was made in r77727 whereas your R-devel appears to be r77715 (so would not exhibit the fixed behaviour). My guess is that there was a perpetual installation failure after r77715 but that the test folder was still retrieved and used. On Sat, 8 Feb 2020 at 19:27, Berwin A Turlach <berwin.turlach at gmail.com> wrote: > >

G'day all, I have daily scripts running to install the patched version of the current R version and the development version of R on my linux box (Ubuntu 18.04.4 LTS). The last development version that was successfully compiled and installed was "R Under development (unstable) (2020-01-25 r77715)" on 27 January. Since then the script always fails as a regression test seems to fail.

On Sat, Feb 8, 2020 at 9:27 AM Berwin A Turlach <berwin.turlach at gmail.com> wrote: > > G'day all, > > I have daily scripts running to install the patched version of the > current R version and the development version of R on my linux box > (Ubuntu 18.04.4 LTS). > > The last development version that was successfully compiled and > installed was "R Under

Hey everyone, I just got one of these today: Nov 10 16:07:54 stormy kernel: sd 0:0:0:0: SCSI error: return code = 0x08000000 Nov 10 16:07:54 stormy kernel: sda: Current: sense key: Medium Error Nov 10 16:07:54 stormy kernel: Add. Sense: Unrecovered read error Nov 10 16:07:54 stormy kernel: Nov 10 16:07:54 stormy kernel: Info fld=0x0 Nov 10 16:07:54 stormy kernel: end_request: I/O error, dev

My interpretation of dput.Rd is that dput() gives an exact ASCII form of the internal representation of an R object. But: rhankin at cuttlefish:~ $ R --version R version 3.6.2 (2019-12-12) -- "Dark and Stormy Night" Copyright (C) 2019 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) [snip] rhankin at cuttlefish:~ $ R --vanilla --quiet > x <-

Hi. Under R-news there is an entry for 3.6.2 patched regarding LAPACK. However, when uncompresding the current R-patched, it creates R-Rc directories. Is this a naming oversight or is the patched version actually the unadjusted release candidate? Thank you, Avi On Thu, Dec 12, 2019 at 4:58 AM Peter Dalgaard via R-devel < r-devel at r-project.org> wrote: > The build system rolled up

On 29/02/2020 4:19 a.m., Ben Bolker wrote: > > I think Robin knows about FAQ 7.31/floating point (author of > 'Brobdingnag', among other numerical packages). I agree that this is > surprising (to me). > > To reframe this question: is there way to get an *exact* ASCII > representation of a numeric value (i.e., guaranteeing the restored value > is identical()

Thank you. I apologize for not providing the link. [1] Under the news for R-revel there is a single entry for R 3.6.2-patched. The file I downloaded was [2] with a date of 2019-12-12 01:50. Is it safe to say that 3.6.2 has the LAPACK upgrades and fixes? Apologies in advance if iOS links the URL below. I cannot access gmail desktop from behind my corporate firewall. Thank you again, Avi [1]

I think Robin knows about FAQ 7.31/floating point (author of 'Brobdingnag', among other numerical packages). I agree that this is surprising (to me). To reframe this question: is there way to get an *exact* ASCII representation of a numeric value (i.e., guaranteeing the restored value is identical() to the original) ? .deparseOpts has ?"digits17"?: Real and finite complex

The build system rolled up R-3.6.2.tar.gz (codename "Dark and Stormy Night") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-3/R-3.6.2.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter

The build system rolled up R-3.6.2.tar.gz (codename "Dark and Stormy Night") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-3/R-3.6.2.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter

The build system rolled up R-3.6.2.tar.gz (codename "Dark and Stormy Night") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-3/R-3.6.2.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter

>>>>> robin hankin >>>>> on Sun, 1 Mar 2020 09:26:24 +1300 writes: > Thanks guys, I guess I should have referred to FAQ 7.31 > (which I am indeed very familiar with) to avoid > misunderstanding. I have always used dput() to clarify > 7.31-type issues. > The description in ?dput implies [to me at any rate] that > there

>>>>> Duncan Murdoch >>>>> on Mon, 2 Mar 2020 04:43:53 -0500 writes: > On 02/03/2020 3:24 a.m., Martin Maechler wrote: >>>>>>> robin hankin >>>>>>> on Sun, 1 Mar 2020 09:26:24 +1300 writes: >> >> > Thanks guys, I guess I should have referred to FAQ 7.31 >> > (which I

It is not obvious what it is that you are calling "R-patched", nor where there could be an entry for "3.6.2 patched". The prerelease/patched versions are snapshots of R-3-6-branch made at 00:20 so the current one will have been made before the release version run started at 09:00 this morning, and hence the nightly tarball will be of the release candidate. However it will not

Thanks guys, I guess I should have referred to FAQ 7.31 (which I am indeed very familiar with) to avoid misunderstanding. I have always used dput() to clarify 7.31-type issues. The description in ?dput implies [to me at any rate] that there will be no floating-point roundoff in its output. I hadn't realised that 'deparsing' as discussed in dput.Rd includes precision roundoff issues.

On 02/03/2020 3:24 a.m., Martin Maechler wrote: >>>>>> robin hankin >>>>>> on Sun, 1 Mar 2020 09:26:24 +1300 writes: > > > Thanks guys, I guess I should have referred to FAQ 7.31 > > (which I am indeed very familiar with) to avoid > > misunderstanding. I have always used dput() to clarify > > 7.31-type

>>>>> G?bor Cs?rdi >>>>> on Thu, 26 Dec 2019 08:23:10 +0000 writes: > Hi Frederick, I know some non R-core people use this > workflow to keep local patches in git branches: > https://bookdown.org/lionel/contributing/ > Best, Gabor Thank you, Gabor, and notably, Lionel, for providing the extras. As Frederik notes / ask as well about

I am trying to put my app on heroku, following the instructions, when I get here I get this error: $ git push heroku master Enter passphrase for key ''/c/Users/Laurence/.ssh/id_rsa'': Counting objects: 277, done. Delta compression using up to 2 threads. Compressing objects: 100% (246/246), done. Read from remote host heroku.com: The connection was aborted fatal: sha1 file