On 18/07/18 22:31, Lars Hupel wrote:
>> In the past 2 days the isabelle_cronjob could not connect to
>> https://isabelle.in.tum.de/repos/isabelle -- but it appears to work from
>> most other hosts that I've tried. Maybe some odd change concerning SSL
>> certificates on the server vs. client side?
In the past 2 days the isabelle_cronjob could not connect to
https://isabelle.in.tum.de/repos/isabelle -- but it appears to work
from
most other hosts that I've tried. Maybe some odd change concerning SSL
certificates on the server vs. client side?
That's indeed strange. There was an issue
In the past 2 days the isabelle_cronjob could not connect to
https://isabelle.in.tum.de/repos/isabelle -- but it appears to work from
most other hosts that I've tried. Maybe some odd change concerning SSL
certificates on the server vs. client side?
To keep the release process going, I've now set
I had what seems to be a spurious failure of
Probabilistic_Timed_Automata yesterday:
https://ci.isabelle.systems/jenkins/job/testboard/50/consoleFull
The error message is:
*** exception THM 0 raised (line 1136 of "thm.ML"): generalize: bad index
I am quite sure that my (purely cosmetic) changes
This is a reminder that we are in the final consolidation phase towards
Isabelle2018-RC2.
I will say more precisely when the fork of the isabelle-dev vs.
isabelle-release repositories will happen, presumably in the next few
days. After return from FLoC I still need to sort out many details, and