OSX VMs get a Java Update dialog after being left on for some time. |
|||||
Issue descriptionI've been doing debugging on vm64-m1 for Issue 515627. One of the things I've noticed is that after a while, a Java Software Update dialog shows up. This almost certainly interferes with some tests, since it probably grabs focus, and also can apply occlusion to Windows. Do we have any idea what's causing it to show up, and can we prevent it? Assigning to dba@, as the resident Mac image expert.
,
Jun 2 2016
I don't know why it was needed to begin with. Adding some more Mac people who might know.
,
Jun 2 2016
I think Java is used for the closure compiler, but I didn't think that it was a requirement of a Chromium build. As far as I know, nothing else should require Java.
,
Jun 2 2016
Do we use the closure compiler for tests? Would it be safe to try removing Java from the OS X image we throw onto new machines?
,
Jun 2 2016
+dbeam for question about closure compiler Depending on dbeam@'s response, I think it would be fine to try removing Java and seeing if anything breaks. Note that if you execute /usr/bin/java when Java is not installed, OS X will prompt you to install it.
,
Jun 2 2016
Can we replace /usr/bin/java with a symlink to a program that always no-ops and returns a failure code? At some point, I expect someone to accidentally sneak in a usage of Java, and don't want it to go undetected.
,
Jun 2 2016
some clarifications: 1) all closure compilation FYI/try bots I run are on Linux, but there may be remoting/ or ios/ things that run on Mac 2) the closure compilation infrastructure should handle a lack of `java` on the $PATH or various other situations and react appropriately, so feel free to throw whatever at it
,
Jun 2 2016
I’m not aware of anything in our build that relies on Java, either the runtime or the toolchain.
,
Jun 2 2016
followup clarification: nothing about closure compilation is required in the build toolchain; it's all optional (i.e. we also wouldn't be adding the requirement to have Java to build any web part of Chrome)
,
Aug 14
This has been fixed for a while. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by d...@chromium.org
, Jun 2 2016