Re: [isabelle-dev] Automated testing questions
On Mon, 18 Mar 2013, Tjark Weber wrote: On Mon, 2013-03-18 at 12:16 +0100, Makarius wrote: If anything is missing or wrong in README_REPOSITORY, I ask once again to point it out, either on isabelle-dev or privately, and not to make unreliable/unmaintained clones of such important information. Occasionally cd isabelle hg pull -u ./bin/isabelle components -a ./bin/isabelle jedit -l HOL results in Scala build errors. If this is bound to happen from time to time, instructions on how to recover (possibly just mentioning -f) or a pointer to such instructions might be helpful. OK, I will take it into account really soon, when rewriting the text once more. (I've again got distracted by too many other things.) Is there anything else for the system manual about isabelle build? Makarius ___ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
Re: [isabelle-dev] Automated testing questions
On Sun, 17 Mar 2013, Clemens Ballarin wrote: Also, which server should I use for pushing my changes to Isabelle so as to avoid repository trouble? isabelle-server.in.tum.de is the canonical entry point for ssh etc. as has been pointed out already. It runs some funny Gentoo Linux, which is totally different from everything else. The classic macbroy2[0-9] hosts were back into proper shape in the past couple of weeks, but just a few days updated again to use rolling releases from some semi-official repository of OpenSUSE. So the thrill is back ... Myself I tend to agree with Mark Shuttleworth, who said about that question for Ubuntu recently, that a rolling release is no release at all. We are faced with constant decline of software quality, and I don't see a need to accelerate that. Makarius ___ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
Re: [isabelle-dev] Automated testing questions
Hi Clemens, On 17.03.2013 20:43, Clemens Ballarin wrote: Dear Developers, What it the current best practice for testing my change to Isabelle? There used to be testboard, but I'm unsure how that evolved. Is there a similar service for testing my change to Isabelle against the AFP? I do use the testboard for bigger changesets. The description from http://www.mail-archive.com/isabelle-dev@mailbroy.informatik.tu-muenchen.de/msg01500.html (Developer-initiated tests) is AFAIK still up to date. Another alternative is to build everything on your own machine, which is feasible thanks to the wonders of PolyML 5.5 and the new build system. All you need to do is to clone the AFP repository, register it as a component (via init_component /path/to/AFP in etc/settings) and follow the instruction from http://www.mail-archive.com/isabelle-dev@mailbroy.informatik.tu-muenchen.de/msg02903.html . Also, which server should I use for pushing my changes to Isabelle so as to avoid repository trouble? lxbroy10 Dmitriy ___ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
Re: [isabelle-dev] Automated testing questions
On Mon, 18 Mar 2013, Dmitriy Traytel wrote: Another alternative is to build everything on your own machine, which is feasible thanks to the wonders of PolyML 5.5 and the new build system. All you need to do is to clone the AFP repository, register it as a component (via init_component /path/to/AFP in etc/settings) and follow the instruction from http://www.mail-archive.com/isabelle-dev@mailbroy.informatik.tu-muenchen.de/msg02903.html That is a slightly dated mail of mine, it has been superseded by proper documentation in the system manual and the continously updated README_REPOSITORY file. The latter also points to isabelle-server.in.tum.de as canonical pull/push host for the conventional collection point of Isabelle changesets. If anything is missing or wrong in README_REPOSITORY, I ask once again to point it out, either on isabelle-dev or privately, and not to make unreliable/unmaintained clones of such important information. Makarius ___ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
Re: [isabelle-dev] Automated testing questions
On Mon, 2013-03-18 at 12:16 +0100, Makarius wrote: If anything is missing or wrong in README_REPOSITORY, I ask once again to point it out, either on isabelle-dev or privately, and not to make unreliable/unmaintained clones of such important information. Occasionally cd isabelle hg pull -u ./bin/isabelle components -a ./bin/isabelle jedit -l HOL results in Scala build errors. If this is bound to happen from time to time, instructions on how to recover (possibly just mentioning -f) or a pointer to such instructions might be helpful. Tjark ___ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
[isabelle-dev] Automated testing questions
Dear Developers, What it the current best practice for testing my change to Isabelle? There used to be testboard, but I'm unsure how that evolved. Is there a similar service for testing my change to Isabelle against the AFP? Also, which server should I use for pushing my changes to Isabelle so as to avoid repository trouble? Clemens ___ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
