[opam-commits] Cron job update-opam-repo failed on opam.ocaml.org

[Louis Gesbert]

This just means the job didn't start because the last one wasn't finished yet.
Seems that the new way to get the package dates is a bit too slow :/
(also, opam2web is run twice, the second time to get the stats of 1.0 which is overkill and really doesn't need to be done every time...)

Le jeudi 21 novembre 2013 21:15:02 cron at opam.ocaml.org a écrit :
> 
> === FULL LOG ===
> 
> 
> ======== RUNNING COMMAND: update-opam-repo update-opam-repo.sh ========
> {{{
> ==> 2013-11-21 21:15:01+00:00
> ==> Load opam env
> ==> Running update-opam-repo.sh
> 
> fatal: destination path '/home/opam/www-new' already exists and is not an empty directory.
> 
> ======== CRON JOB update-opam-repo FAILED ========
> ==> 2013-11-21 21:15:01+00:00
> ==> Full command was: update-opam-repo.sh
> _______________________________________________
> Opam-commits mailing list
> Opam-commits at lists.ocaml.org
> http://lists.ocaml.org/listinfo/opam-commits
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/opam-commits/attachments/20131121/839fa3e2/attachment.html>