You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Ganesh Raju <ga...@linaro.org> on 2017/03/23 14:36:51 UTC
Fwd: Build failed due to OpenJDK 1.8.0_121 changes
Forwarding to dev mailing list. Any thoughts ?
Thanks
Ganesh Raju
---------- Forwarded message ----------
From: Jun He <ju...@linaro.org>
Date: Thu, Mar 23, 2017 at 5:10 AM
Subject: Build failed due to OpenJDK 1.8.0_121 changes
To: Roman Shaposhnik <rv...@apache.org>, Ganesh Raju <ga...@linaro.org>
Cc: Naresh Bhat <na...@linaro.org>, Eugene Xie <eu...@linaro.org>,
Tone Zhang <to...@linaro.org>, Yuqi Gu <yu...@linaro.org>
Hi, Roman,
Two components: ignite-hadoop, solr are failed to build when open-jdk-8_121
is used.
There are discussions for this issue:
https://issues.apache.org/jira/browse/IGNITE-4770
https://issues.apache.org/jira/browse/LUCENE-7651
http://mail.openjdk.java.net/pipermail/javadoc-dev/2017-January/000281.html
This jdk change should also impact x86_64/ppc64 build.
We did a test today on a X86_64 server:
./gradlew -POS=ubuntu-16.04 -Pprefix=1.1.0 bigtop-slaves
docker run -v `pwd`:/ws bigtop/slaves:1.1.0-ubuntu-16.04 bash -l -c 'cd /ws
; gradle solr-rpm'
It also failed as aarch64.
Now for the CI result, I believe that those two components passed build on
x86-64/ppc64 is because the docker images are using open-jdk-1.8.0_111
while aarch64's image uses 1.8.0_121.
So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
see two ways:
1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/
manifests/jdk.pp
2. Rebase patches from upstream to active version in bigtop
(ignite-1.5.0.final, solr-4.10.4)
What's your suggestion for this?
Thanks & regards,
Jun
--
IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Konstantin Boudnik <co...@apache.org>.
With any luck we are going to upgrade to Ignite 1.9 which has this issue fixed.
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Thu, Mar 23, 2017 at 7:36 AM, Ganesh Raju <ga...@linaro.org> wrote:
> Forwarding to dev mailing list. Any thoughts ?
>
> Thanks
> Ganesh Raju
>
>
> ---------- Forwarded message ----------
> From: Jun He <ju...@linaro.org>
> Date: Thu, Mar 23, 2017 at 5:10 AM
> Subject: Build failed due to OpenJDK 1.8.0_121 changes
> To: Roman Shaposhnik <rv...@apache.org>, Ganesh Raju <ga...@linaro.org>
> Cc: Naresh Bhat <na...@linaro.org>, Eugene Xie <eu...@linaro.org>,
> Tone Zhang <to...@linaro.org>, Yuqi Gu <yu...@linaro.org>
>
>
> Hi, Roman,
>
> Two components: ignite-hadoop, solr are failed to build when open-jdk-8_121
> is used.
> There are discussions for this issue:
>
> https://issues.apache.org/jira/browse/IGNITE-4770
> https://issues.apache.org/jira/browse/LUCENE-7651
> http://mail.openjdk.java.net/pipermail/javadoc-dev/2017-January/000281.html
>
> This jdk change should also impact x86_64/ppc64 build.
> We did a test today on a X86_64 server:
>
> ./gradlew -POS=ubuntu-16.04 -Pprefix=1.1.0 bigtop-slaves
> docker run -v `pwd`:/ws bigtop/slaves:1.1.0-ubuntu-16.04 bash -l -c 'cd /ws
> ; gradle solr-rpm'
>
> It also failed as aarch64.
>
> Now for the CI result, I believe that those two components passed build on
> x86-64/ppc64 is because the docker images are using open-jdk-1.8.0_111
> while aarch64's image uses 1.8.0_121.
>
> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
> see two ways:
> 1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/
> manifests/jdk.pp
> 2. Rebase patches from upstream to active version in bigtop
> (ignite-1.5.0.final, solr-4.10.4)
>
> What's your suggestion for this?
>
> Thanks & regards,
>
> Jun
>
>
>
>
> --
> IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Jun He <ju...@linaro.org>.
Hi,
I created two JIRA for openjdk-8u_121 issue.
https://issues.apache.org/jira/browse/BIGTOP-2716
https://issues.apache.org/jira/browse/BIGTOP-2717
Two patches which rebased upstream fix to version used in bigtop are
uploaded. Please help to check.
If downgrade jdk is not feasible, maybe we can use this way to fix the
build issue.
Thanks & regards,
Jun
On 24 March 2017 at 10:31, Ganesh Raju <ga...@linaro.org> wrote:
> Here is the link for 1.8.0_111
> https://launchpad.net/~openjdk-r/+archive/ubuntu/security/+build/11087717
>
> Thanks,
> Ganesh
>
> On Thu, Mar 23, 2017 at 3:28 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
>
>> >>
>> >> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04
>> I
>> >> see two ways:
>> >> 1. Downgrade open-jdk to 1.8.0_111. This needs to change
>> bigtop_toolchain/
>> >> manifests/jdk.pp
>> >
>> > I'd vote for this option. But I've got to ask: where do I get that
>> exact version
>> > for ubuntu 16.04?
>>
>> You can find the available packages here
>> http://security.ubuntu.com/ubuntu/pool/main/o/openjdk-8/
>>
>> Olaf
>>
>>
>> >
>> > Thanks,
>> > Roman.
>>
>>
>
>
> --
> IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
>
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Ganesh Raju <ga...@linaro.org>.
Here is the link for 1.8.0_111
https://launchpad.net/~openjdk-r/+archive/ubuntu/security/+build/11087717
Thanks,
Ganesh
On Thu, Mar 23, 2017 at 3:28 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
> >>
> >> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
> >> see two ways:
> >> 1. Downgrade open-jdk to 1.8.0_111. This needs to change
> bigtop_toolchain/
> >> manifests/jdk.pp
> >
> > I'd vote for this option. But I've got to ask: where do I get that exact
> version
> > for ubuntu 16.04?
>
> You can find the available packages here
> http://security.ubuntu.com/ubuntu/pool/main/o/openjdk-8/
>
> Olaf
>
>
> >
> > Thanks,
> > Roman.
>
>
--
IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Olaf Flebbe <of...@oflebbe.de>.
> Am 23.03.2017 um 21:33 schrieb Roman Shaposhnik <ro...@shaposhnik.org>:
>
> There's no 111 :-(
Yep, ubuntu seems to have replaced all 111 packages by 121. And yes, our current docker image still has 111. My-o-my.
Guess going back is no option, at least not without compiling java ourself or grabbing it from a dubious site.
When I understood the problem correctly it is possible to work around the issue by supplying a command line switch to javadoc.
Problem is one cannot detect easily if the switch is necessary or not.
Olaf
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
There's no 111 :-(
Jun, Naresh, Ganesh, out of the list available on the URL Olaf
provided -- what should we pick?
Thanks,
Roman.
On Thu, Mar 23, 2017 at 1:28 PM, Olaf Flebbe <of...@oflebbe.de> wrote:
>>>
>>> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
>>> see two ways:
>>> 1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/
>>> manifests/jdk.pp
>>
>> I'd vote for this option. But I've got to ask: where do I get that exact version
>> for ubuntu 16.04?
>
> You can find the available packages here
> http://security.ubuntu.com/ubuntu/pool/main/o/openjdk-8/
>
> Olaf
>
>
>>
>> Thanks,
>> Roman.
>
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Olaf Flebbe <of...@oflebbe.de>.
>>
>> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
>> see two ways:
>> 1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/
>> manifests/jdk.pp
>
> I'd vote for this option. But I've got to ask: where do I get that exact version
> for ubuntu 16.04?
You can find the available packages here
http://security.ubuntu.com/ubuntu/pool/main/o/openjdk-8/
Olaf
>
> Thanks,
> Roman.
Re: Build failed due to OpenJDK 1.8.0_121 changes
Posted by Roman Shaposhnik <rv...@apache.org>.
On Thu, Mar 23, 2017 at 7:36 AM, Ganesh Raju <ga...@linaro.org> wrote:
> Forwarding to dev mailing list. Any thoughts ?
>
> Thanks
> Ganesh Raju
>
>
> ---------- Forwarded message ----------
> From: Jun He <ju...@linaro.org>
> Date: Thu, Mar 23, 2017 at 5:10 AM
> Subject: Build failed due to OpenJDK 1.8.0_121 changes
> To: Roman Shaposhnik <rv...@apache.org>, Ganesh Raju <ga...@linaro.org>
> Cc: Naresh Bhat <na...@linaro.org>, Eugene Xie <eu...@linaro.org>,
> Tone Zhang <to...@linaro.org>, Yuqi Gu <yu...@linaro.org>
>
>
> Hi, Roman,
>
> Two components: ignite-hadoop, solr are failed to build when open-jdk-8_121
> is used.
> There are discussions for this issue:
>
> https://issues.apache.org/jira/browse/IGNITE-4770
> https://issues.apache.org/jira/browse/LUCENE-7651
> http://mail.openjdk.java.net/pipermail/javadoc-dev/2017-January/000281.html
>
> This jdk change should also impact x86_64/ppc64 build.
> We did a test today on a X86_64 server:
>
> ./gradlew -POS=ubuntu-16.04 -Pprefix=1.1.0 bigtop-slaves
> docker run -v `pwd`:/ws bigtop/slaves:1.1.0-ubuntu-16.04 bash -l -c 'cd /ws
> ; gradle solr-rpm'
>
> It also failed as aarch64.
>
> Now for the CI result, I believe that those two components passed build on
> x86-64/ppc64 is because the docker images are using open-jdk-1.8.0_111
> while aarch64's image uses 1.8.0_121.
>
> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
> see two ways:
> 1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/
> manifests/jdk.pp
I'd vote for this option. But I've got to ask: where do I get that exact version
for ubuntu 16.04?
Thanks,
Roman.