[R-pkg-devel] Unable to reproduce reported problems. Docker image?

| I am currently trying to submit a package to CRAN, and I see no problems in running the test on my package on Linux ubuntu 18.04 and the latest compiled R.
| Is there a docker image of the CRAN automatic build system so that one can try to reproduce the problem in house?

In short, no.

There are Docker containers provided by the Rocker Project, by RHub, and by
others, but none of these _exactly_ match the CRAN containers.  Closing this
gap has been discussed, alas time is short and limited so nuttin' to show. 

Dirk

http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

No, for Windows you may use winbuilder that comes very close. More 
generally you can try r-hub for all OSes, but that is less close.

Best,
Uwe Ligges

I am currently trying to submit a package to CRAN, and I see no problems in running the test on my package on Linux ubuntu 18.04 and the latest compiled R.
Is there a docker image of the CRAN automatic build system so that one can try to reproduce the problem in house?

Thanks

________________________________


AstraZeneca UK Limited is a company incorporated in En...{{dropped:8}}

Thanks. What is the recommended strategy in this case? Keep submitting and patching until it passes?

| I am currently trying to submit a package to CRAN, and I see no problems in running the test on my package on Linux ubuntu 18.04 and the latest compiled R.
    | Is there a docker image of the CRAN automatic build system so that one can try to reproduce the problem in house?

    In short, no.

    There are Docker containers provided by the Rocker Project, by RHub, and by
    others, but none of these _exactly_ match the CRAN containers.  Closing this
    gap has been discussed, alas time is short and limited so nuttin' to show.

    Dirk

    --
    https://clicktime.symantec.com/39by3e5jiumtscrjhg8uNwd6H2?u=http%3A%2F%2Fdirk.eddelbuettel.com | @eddelbuettel | edd at debian.org


________________________________


AstraZeneca UK Limited is a company incorporated in England and Wales with registered number:03674842 and its registered office at 1 Francis Crick Avenue, Cambridge Biomedical Campus, Cambridge, CB2 0AA.

This e-mail and its attachments are intended for the above named recipient only and may contain confidential and privileged information. If they have come to you in error, you must not copy or show them to anyone; instead, please reply to this e-mail, highlighting the error to the sender and then immediately delete the message. For information about how AstraZeneca UK Limited and its affiliates may process information, personal data and monitor communications, please see our privacy notice at www.astrazeneca.com<https://www.astrazeneca.com>

| Thanks. What is the recommended strategy in this case? Keep submitting and patching until it passes?

Standard debugging, and (as Uwe already said) win-builder for that OS, rhub
for others, and asking here, ...  Imperfect, but doable.

It would be so nice to have actual Docker containers to reproduce issues.
Maybe one day.

Dirk

http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

it probably makes sense to more directly indicate what package is causing problems (e.g., sharing the location of a public repository of the source) and the nature of the error (cut-and-paste the check output here?). Likely this will lead both to insight into the problem being flagged by the builder, and the reason why you are not able to reproduce it.

Martin Morgan 

?On 1/31/20, 9:04 AM, "R-package-devel on behalf of Dirk Eddelbuettel" <r-package-devel-bounces at r-project.org on behalf of edd at debian.org> wrote:

| Thanks. What is the recommended strategy in this case? Keep submitting and patching until it passes?
    
    Standard debugging, and (as Uwe already said) win-builder for that OS, rhub
    for others, and asking here, ...  Imperfect, but doable.
    
    It would be so nice to have actual Docker containers to reproduce issues.
    Maybe one day.
    
    Dirk
    
    -- 
    http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
    
    ______________________________________________
    R-package-devel at r-project.org mailing list
    https://stat.ethz.ch/mailman/listinfo/r-package-devel

I think (but I am not sure) that I narrowed down the issue to a stochastic process that has no seed defined. Unfortunately it's not my package so I have to do mostly guesswork on this regard.
What has surprised me though, is that I managed to get exact same results on three different platforms (linux, mac, windows) and three different versions (3.4, 3.5.3, and development), but the only platform that shows the variation is the CRAN one. Only when I added a single throwaway sample() call I got the same behaviour on my machines.

Thank you for your help.

it probably makes sense to more directly indicate what package is causing problems (e.g., sharing the location of a public repository of the source) and the nature of the error (cut-and-paste the check output here?). Likely this will lead both to insight into the problem being flagged by the builder, and the reason why you are not able to reproduce it.

    Martin Morgan

| Thanks. What is the recommended strategy in this case? Keep submitting and patching until it passes?

        Standard debugging, and (as Uwe already said) win-builder for that OS, rhub
        for others, and asking here, ...  Imperfect, but doable.

        It would be so nice to have actual Docker containers to reproduce issues.
        Maybe one day.

        Dirk

        --
        https://clicktime.symantec.com/3LGnbPsU527tgDjdhmUzsay6H2?u=http%3A%2F%2Fdirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

        ______________________________________________
        R-package-devel at r-project.org mailing list
        https://clicktime.symantec.com/3Pzw1p1VBawxJbHABzaUeBq6H2?u=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel



________________________________


AstraZeneca UK Limited is a company incorporated in England and Wales with registered number:03674842 and its registered office at 1 Francis Crick Avenue, Cambridge Biomedical Campus, Cambridge, CB2 0AA.

This e-mail and its attachments are intended for the above named recipient only and may contain confidential and privileged information. If they have come to you in error, you must not copy or show them to anyone; instead, please reply to this e-mail, highlighting the error to the sender and then immediately delete the message. For information about how AstraZeneca UK Limited and its affiliates may process information, personal data and monitor communications, please see our privacy notice at www.astrazeneca.com<https://www.astrazeneca.com>