similar to: Request for help with UBSAN and total absense of CRAN response

----- Original Message ----- > From: "Dirk Eddelbuettel" <edd at debian.org> > To: r-devel at r-project.org > Cc: "Erik Bernhardsson" <erik at malfunction.org>, "Dirk Eddelbuettel" <edd at debian.org> > Sent: Tuesday, January 13, 2015 7:30:47 AM > Subject: [Rd] Request for help with UBSAN and total absense of CRAN response > >

Dirk, The vagrant setup I use to test my packages with UBSAN also seems to replicate the error reported by CRAN (together with some other warnings). I have attached the files (I hope they get through the filters). I suppose you know what to do with them. Jan Dirk Eddelbuettel <edd at debian.org> schreef: > CRAN has a package of mine in upload limbo because it failed UBSAN.

Dear All, I'm trying to implement the section of the manual pertaining to the gcc-ubsan test carried by CRAN on my local computer (ubuntu 14.04): http://www.stats.ox.ac.uk/pub/bdr/memtests/gcc-UBSAN/README.txt I was wondering whether someone could tell what the minimal version of the gcc tool chain needed to run the gcc-ASAN and gcc-UBSAN alignment tests on ones local

Dear all, bigKRLS, which has been on CRAN for a couple of years, had to be pulled recently due to what seems to be a sanitizer issue stemming from its use of bigmemory. bigKRLS works fine (we?ve used it ourselves on many different platforms and have had over 15,000 downloads without an end user reporting difficulties because of this issue). Unfortunately, we have been unable to reproduce the

One of my packages is slated to be archived from CRAN due to failures when the ATLAS BLAS is used. I am unable to replicate the error on my machine under R 3.6.1 using the atlas library from ubuntu (seems to be 3.10.2-9, while the good professor is using 3.10.3 per https://www.stats.ox.ac.uk/pub/bdr/Rblas/README.txt ). I also tried the rocker/r-base with R 3.6.2 and

On 13 January 2015 at 08:21, Dan Tenenbaum wrote: | Where should the package source be downloaded from? I see it in CRAN (but presumably the latest version that causes the issue is not yet downloadable) and in github. The "presumable" assumption is incorrect AFAIK. The error should presumably came up in both versions as annoylib.h did not change there. Feel free to prove me wrong :)

Hi all, Nice one for a Friday afternoon ... I'm trying to follow this section of the manual : http://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Using-Undefined-Behaviour-Sanitizer to build R-devel (as of a few hours ago: rev 66684) with -fsanitize=undefined,address. My OS is Linux Mint Debian Edition. To get gcc-4.9 I added Debian testing to my apt sources and ran : sudo

Dear Prof. Ripley, Thank you for your answer. I think I am way over my head here. (Using Doker adds a level of complexity that I'm afraid I can't manage for now so I am happy with building Rdevel and using it in to run these tests). After building Rdevel with what I think are the correct options** (just to avoid mistakes I have also fully removed R from my system just before and

Hi: I have a Dockerfile, which builds an image which installed R 3.3.2 in Ubuntu 14.04, but building using that Dockerfile seems to have stopped working and I am unclear why. I believe the relevant error is: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet

On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net> wrote: > Winston, > I had a similar experience to you tracking down an insanely difficult bug > in my R code that "disappeared" whenever slight changes were made to the > script (e.g. like adding cat() statements). In my case, it coincided with > my over-eager compilation of R and its

Hi Dave and Dirk, sorry, I do not understand half of this, as I do not use docker myself. Buf if Dirk does not use Debian buster as the basis for his Rocker container, then you should probably not try to install the backport to buster. Shouldn't these docker containers be there to avoid the need to install R? Johannes Am Montag, 22. Juni 2020, 19:15:56 CEST schrieb Dirk Eddelbuettel:

On 04/29/2018 09:30 AM, Jeroen Ooms wrote: > On Sat, Apr 28, 2018 at 10:00 PM, Michael Rutter <marutter at gmail.com> wrote: >> These have not been mirrored to CRAN as I want to have the other r-cran >> packages built against R 3.5 before adding to CRAN. Worried about breaking >> working systems currently on R 3.4.4. > > Thanks, Michael. I did some simple tests,

I continue to receive an error installing R via dockerfile on a buster image python:3. E: The value 'buster-cran40' is invalid for APT::Default-Release as such a release is not available in the sources My starting point is the debian buster based Python:3 image adding a couple of python specific configurations and then using the commands in the R project documentation for installing R on

Hi Dirk, I too would need to get R-devel on my Ubuntu box (alongside an existing R installation) to check my packages, especially given the mayhem that awaits us when the new `R CMD check --as-cran` goes live. ( http://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html ) I was wondering if the script that you posted on r-sig-debian a couple years back was still valid. More however, I'd like to

My dockerfile: FROM python:3 WORKDIR /usr/src/app COPY requirements.txt ./ COPY languageserver-master ./ COPY radian-master ./ RUN pip3 install --no-cache-dir -r requirements.txt EXPOSE 8080 RUN apt-key adv --keyserver keys.gnupg.net --recv-key 'E19F5F87128899B192B1A2C2AD5F960A256A04AF' RUN echo "deb http://cloud.r-project.org/bin/linux/debian buster-cran40/" >>

Count me as a docker newbie building a debian python and R mytools container. My first post. This was working a couple of weeks ago. My last successful build was a R 4.01 release when the R:base docker hub project used to list a number of base images and I used sections of a posted docker file in that area. Then the install directions at Cran:R listed buster:4.01 instructions that I also added to

On 21 November 2019 at 17:57, Martin Maechler wrote: | (if you use a version of R-devel, with svn rev >= 77446; which | you may get as a binary for Windows in about one day; everyone | else needs to compile for the sources .. or wait a bit, maybe | also not much longer than one day, for a docker image) : FYI: rocker/drd [1] and rocker/r-devel both have rev 77455 now (as they are both on

On 12 February 2017 at 12:28, Jeroen Ooms wrote: | On Mon, Dec 19, 2016 at 2:27 PM, Terje J?rgensen <terjej at imr.no> wrote: | > Hi, | > | > I am unable to install tibble, a required package for ggplot2 in R. I am | > running R (version 3.3.2 ) in RStudio (version 1.0.44). My OS is ubuntu | > 14.04 (64 bits). | | I was able to reproduce this problem. What happened is that

On 13/10/2015 14:46, kaveh wrote: > Dear All, > > I'm trying to implement the section of the manual pertaining to the > gcc-ubsan test > carried by CRAN on my local computer (ubuntu 14.04): > > http://www.stats.ox.ac.uk/pub/bdr/memtests/gcc-UBSAN/README.txt > > I was wondering whether someone could tell what the minimal version > of the gcc tool

I've been working on adding UBSan support to CMake (so that errors found by it can be uploaded to CDash for viewing). One problem is that the message is very generic. The patch here addes 'UndefinedBehaviorSanitizer' to the message so that they may be detected more easily. If something else is wanted (such as the '===' lines from ASan or TSan to cope with things like printing