Re: CI failed to use javac 1.8

On 18 July 2016 at 09:31, Roy Golan wrote: > > > On 17 July 2016 at 14:50, Barak Korren wrote: >> >> More info: >> >> This patch sorted this out for master: https://gerrit.ovirt.org/#/c/46516/ >> I guess we can't just use it for 3.6 because we still need to

Re: CI failed to use javac 1.8

On 17 July 2016 at 14:50, Barak Korren wrote: > More info: > > This patch sorted this out for master: https://gerrit.ovirt.org/#/c/46516/ > I guess we can't just use it for 3.6 because we still need to support > el6 and java 1.7. > > jdk8 is supported and installed on el6 and

Re: CI failed to use javac 1.8

More info: This patch sorted this out for master: https://gerrit.ovirt.org/#/c/46516/ I guess we can't just use it for 3.6 because we still need to support el6 and java 1.7. On 17 July 2016 at 14:29, Barak Korren wrote: > Looking deeper into this, I see the following

Re: CI failed to use javac 1.8

Looking deeper into this, I see the following difference in the Mock setup logs between this run and the last successful one: For this run, these are the java packages that are installed: DEBUG util.py:417: java-1.8.0-openjdk-headlessx86_64 1:1.8.0.92-4.b14.fc23 updates 32 M For

Re: CI failed to use javac 1.8

On 17 July 2016 at 13:38, Eyal Edri wrote: > Might be related to new vms installed recently. > > Barak, can you have a look? Maybe puppet didn't run.. > This is a standard-CI job, so probably unrelated to VM configuration. > On Jul 17, 2016 1:25 PM, "Roy Golan"

Re: CI failed to use javac 1.8

Might be related to new vms installed recently. Barak, can you have a look? Maybe puppet didn't run.. On Jul 17, 2016 1:25 PM, "Roy Golan" wrote: > This job just failed after merged cause it didn't find javac > > >

CI failed to use javac 1.8

This job just failed after merged cause it didn't find javac http://jenkins.ovirt.org/job/ovirt-engine_3.6_check-merged-fc23-x86_64/88/console An excerpt from the error: ``` *08:55:42* [INFO] *08:55:42* [ERROR] Failed to