Hi Herve, Thanks a lot for the explanation; mystery solved. And yes, I can now see the updated report.
Best, R. On Sat, 09-February-2019, at 10:54:40, Pages, Herve <hpa...@fredhutch.org> wrote: > Hi Ramon, > > We run the software builds every night and normally the build report > gets updated every morning (for the people on the East Coast). However > sometimes things don't work as expected. This time the builds went fine > but the script that updates the report failed so that's why we still see > the report from the day before. However, it seems that OncoSimulR 2.13.1 > passed 'R CMD check' on all platforms and propagated so this is why you > see it on the package landing page. > > I addressed the issue with the script so hopefully the report will get > updated today around 10 am EST. We should see OncoSimulR 2.13.1 on this > new report. > > Best, > > H. > > On 2/9/19 01:13, Ramon Diaz-Uriarte wrote: >> Dear All, >> >> For the development version of a package, I thought that a new version of a >> package (a new version of the archive) was only made available if and when >> the build/check reports had been passed (for the corresponding OS). But now >> I think I am wrong. >> >> >> For a package I maintain, OncoSimulR, I am seeing package archives for the >> new version (2.13.1) that correspond to the changes I pushed a couple of >> days ago, on 2019-02-07 >> (https://urldefense.proofpoint.com/v2/url?u=https-3A__bioconductor.org_packages_3.9_bioc_html_OncoSimulR.html&d=DwIDaQ&c=eRAMFD45gAfqt84VtBcfhQ&r=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA&m=O0cn-X5Sr3_HhPWuSmTxh06I6kzACAP-AsUKsDNCnEU&s=y8Ni6d5RDqXiSzMWYbsOa6z3CQCHAnB7ViGb_iYe70Y&e=); >> but the >> build report >> (https://urldefense.proofpoint.com/v2/url?u=https-3A__bioconductor.org_checkResults_3.9_bioc-2DLATEST_OncoSimulR_&d=DwIDaQ&c=eRAMFD45gAfqt84VtBcfhQ&r=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA&m=O0cn-X5Sr3_HhPWuSmTxh06I6kzACAP-AsUKsDNCnEU&s=rYQOEwOloojsIaUf3cwDap2VkbgGYyzQjuXOcHMFVmI&e=) >> is >> still showing the build/check from the previous version (2.13.0), which was >> the one that existed at the time of the snapshot date (2019-02-06 17:01:03 >> -0500) of the report. >> >> >> Does this mean that a build bin was executed (I presume successfully) >> shortly after I pushed changes? I think it must, given the "Packaged" stamp >> in the DESCRIPTION file of the three compressed files (which shows >> "2019-02-08 01:19:24 UTC; biocbuild" and similar strings). What about the >> install and check tests? >> >> >> Sorry if this has been explained before. I've looked around but could not >> find any info about it. >> >> >> Thanks, >> >> >> R. >> >> >> -- >> Ramon Diaz-Uriarte >> Department of Biochemistry, Lab B-25 >> Facultad de Medicina >> Universidad Autónoma de Madrid >> Arzobispo Morcillo, 4 >> 28029 Madrid >> Spain >> >> Phone: +34-91-497-2412 >> >> Email: rdia...@gmail.com >> ramon.d...@iib.uam.es >> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__ligarto.org_rdiaz&d=DwIDaQ&c=eRAMFD45gAfqt84VtBcfhQ&r=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA&m=O0cn-X5Sr3_HhPWuSmTxh06I6kzACAP-AsUKsDNCnEU&s=lwENxLhyf-d-fQHkWDDmw2N9LcJ9lgfIY10F4SMCJx8&e= >> >> _______________________________________________ >> Bioc-devel@r-project.org mailing list >> https://urldefense.proofpoint.com/v2/url?u=https-3A__stat.ethz.ch_mailman_listinfo_bioc-2Ddevel&d=DwIDaQ&c=eRAMFD45gAfqt84VtBcfhQ&r=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA&m=O0cn-X5Sr3_HhPWuSmTxh06I6kzACAP-AsUKsDNCnEU&s=BpOP1oelpZxdAeeLjqgmTXtZNUxHirmC3nDujcXKJeo&e= -- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-25 Facultad de Medicina Universidad Autónoma de Madrid Arzobispo Morcillo, 4 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdia...@gmail.com ramon.d...@iib.uam.es http://ligarto.org/rdiaz _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
