Hallo,
on 158c513a39f5, I just had a JVM crash during "isabelle build" when it
was building Isabelle/Scala. (Log attached).
When I did "isabelle build" again, it proceeded to build the Pure
session without problems. However, when I then tried to build
HOL-Computational_Algebra, it stopped and
> on 158c513a39f5, I just had a JVM crash during "isabelle build" when it
> was building Isabelle/Scala. (Log attached).
I had a similar problem today. Unfortunately I didn't save the logfile.
Cheers
Lars
___
isabelle-dev mailing list
On 19/08/17 17:16, Manuel Eberl wrote:
>
> on 158c513a39f5, I just had a JVM crash during "isabelle build" when it
> was building Isabelle/Scala.
Since the JVM crash happened during scalac compilation, I recommend to
enforce a fresh build, e.g. like this:
isabelle jedit -b -f
> Log attached
On 19/08/17 20:31, Manuel Eberl wrote:
>> If you still have that, can you send it to me?
>
> Sure.
>
>> Since the JVM crash happened during scalac compilation, I recommend to
>> enforce a fresh build, e.g. like this:
The log says "java_command: isabelle.Isabelle_Tool build -b
HOL-Analysis" so
The following seems to be the most reliable way to trigger the problem:
while true
isabelle build -b -c Pure
end
I did that and about 6% of builds with Scala 2.12.3 failed with
something like the attached log. I then tried the same thing with Scala
2.12.2 (double-checked "isabelle scala
> If you still have that, can you send it to me?
Sure.
> Since the JVM crash happened during scalac compilation, I recommend to
> enforce a fresh build, e.g. like this:
That seems to have worked. The only output I got was this:
### Building Isabelle/Scala ...
### Building Isabelle/jEdit ...
The Ryzen thing was also on my mind, but I have not experienced any of
those instability issues. From what I read, they are extremely rare
under normal use and the error occured a few seconds after initiating
isabelle build.
Besides, I know that Lars does not have a Ryzen CPU, and it would be a
On 19/08/17 21:14, Manuel Eberl wrote:
>
> As for Scala, could a problem in the Scala compiler really lead to the
> JVM segfaulting? I would have thought if the JVM segfaults, that's a bug
> in the JVM. (unless it's a hardware-related issue, of course)
>
> So, all in all, my money would be on
On 19/08/17 21:27, Makarius wrote:
> I propose to try the previous Scala release locally, e.g. as follows in
> $ISABELLE_HOME_USER/etc/settings:
>
> init_component "$HOME/.isabelle/contrib/scala-2.12.2"
Do not forget "isabelle jedit -b -f" after flipping Scala versions (that
is not required
On 19/08/17 17:19, Lars Hupel wrote:
>> on 158c513a39f5, I just had a JVM crash during "isabelle build" when it
>> was building Isabelle/Scala. (Log attached).
>
> I had a similar problem today. Unfortunately I didn't save the logfile.
Can you say anything about the system? Hardware, OS etc.
10 matches
Mail list logo
