You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Evans Ye <ev...@apache.org> on 2017/07/01 17:31:05 UTC
Releasing 1.2.1
Hi folks,
As you may see I'm working on the 1.2.1 release right now.
Basically what I did is to merge the master branch into branch-1.2 and have
branch-1.2 and release-1.2.1-RC0 tag pushed.
Then, I follow the release guide[1] to walk down the path.
However, I'm currently stuck at:
mvn deploy -Prelease -f bigtop-test-framework/pom.xml
...
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.153 sec
Running org.apache.bigtop.itest.posix.AlternativeTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.411 sec
<<< FAILURE!
Running org.apache.bigtop.itest.posix.ServiceTest
Status []
Tests run: 2, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.04 sec
Running org.apache.bigtop.itest.posix.UGITest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec
Running org.apache.bigtop.itest.shell.ShellTest
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
<<< FAILURE!
Running org.apache.bigtop.itest.TestContractGroovy
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec
Running org.apache.bigtop.itest.TestContractJava
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.bigtop.itest.TestContractJavaProc
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.bigtop.itest.TestListUtilsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec
Results :
Failed tests:
testGetAllAlternatives(org.apache.bigtop.itest.posix.AlternativeTest)
regularUserShell(org.apache.bigtop.itest.shell.ShellTest)
Tests run: 45, Failures: 2, Errors: 0, Skipped: 1
I wonder is it an env issue? I've tried to build on ubuntu-16.04, debian-8,
and centos-7.
ubuntu-16.04 and debian-8 are the same(2 failures), but I got even more
failed tests on centos-7.
To attach more info, here's how I prepare my env:
$ docker run -ti --rm -v $PWD:/tmp bigtop/slaves:trunk-ubuntu-16.04 bash -l
$ cp -r /tmp/.gnupg ~/
$ cd $(BIGTOP_REPO)
$ mvn deploy -Prelease -f bigtop-test-framework/pom.xml
I guess Cos and Roman who has done the release can give me more hints?
Evans
[1]. https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Hi all,
I'm slowly finalizing 1.2.1 release. Please hang on.
Will do an announcement when everything is ready.
Best,
Evans
2017-10-14 17:23 GMT+08:00 Evans Ye <ev...@apache.org>:
> More test have been done for 1.2.1 release.
>
> https://ci.bigtop.apache.org/job/Bigtop-1.2.1-installation
>
> This job tests whether packages can be installed cleanly with pgp
> verification
>
> Though not all the packages can be successfully installed due to
> conflicts, most of them are good.
>
> Following are packages failed to install:
>
> CentOS, Fedora:
> qfs-python.x86_64
>
> OpenSuSE:
> Hue, Oozie
>
> Debian, Ubuntu:
> Hue, Oozie, Phoenix, QFS
>
>
>
>
> 2017-10-13 3:39 GMT+08:00 Evans Ye <ev...@apache.org>:
>
>> AFAIK, the build slave for arm is offline in our CI:
>>
>> docker-slave-arm-1
>> <https://ci.bigtop.apache.org/computer/docker-slave-arm-1/> (offline)
>>
>> If you can get it back into business, then there's no reason not to
>> include it as long as it's in good shape.
>>
>> 2017-10-13 3:31 GMT+08:00 Ganesh Raju <ga...@linaro.org>:
>>
>>> Evans
>>>
>>> What is needed to reestablish the CI builds for Aarch? We are ready to
>>> help
>>> that getting setup as well
>>> We have setup CI builds internally in Linaro which has been working fine.
>>>
>>> Do you need access to the two arm systems for builds?
>>>
>>>
>>> Thanks,
>>> Ganesh
>>>
>>> On Thu, Oct 12, 2017 at 1:56 PM, Evans Ye <ev...@apache.org> wrote:
>>>
>>> > Thanks Kevin for doing the investigation. That is addressed in
>>> BIGTOP-2904.
>>> >
>>> > Regarding to 1.2.1 release. I've finally crossed the finish line and
>>> have
>>> > put it up for a vote.
>>> > Let me share some of the details here:
>>> >
>>> > * All the signed repos are on repos.bigtop.apache.org, which is
>>> backed by
>>> > our new S3 directory
>>> > * Deployment evaluated by
>>> > https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-1.
>>> > 2.1-deployments/,
>>> > which installs packages from repos.bigtop.apache.org. Surely we've
>>> some
>>> > red
>>> > dots, but those problems are also in 1.2.0 as well. 1.2.1 actually
>>> > improves/fixes things that was broken in 1.2.0.
>>> > * Binary convenient artifacts are not available for PPC64LE, but we can
>>> > still put them up afterwards.
>>> >
>>> > Thanks for everyone who helped making this release happening.
>>> > The release stuffs are in the [VOTE] mailing thread. If you've time.
>>> Please
>>> > give it try and provide your feedback.
>>> >
>>> >
>>> > Evans
>>> >
>>> >
>>> >
>>> > 2017-10-10 2:02 GMT+08:00 Kevin Monroe <ke...@canonical.com>:
>>> >
>>> > > Hey Evans, ubuntu 16.04 seems ok from your CI link, but fedora 25
>>> has a
>>> > > problem:
>>> > >
>>> > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1-ppc64le/OS=
>>> > > fedora-25-ppc64le/lastFailedBuild/console
>>> > >
>>> > > I *think* I've tracked this down to the location of protobuf. Note
>>> the
>>> > URL
>>> > > for rpm-based ppc64le distros:
>>> > >
>>> > > https://github.com/apache/bigtop/blob/master/bigtop_
>>> > > toolchain/manifests/protobuf.pp#L54
>>> > >
>>> > > Those fedora-22 URLs are no longer valid:
>>> > >
>>> > > https://dl.fedoraproject.org/pub/fedora-secondary/releases/
>>> > > 22/Everything/ppc64le/
>>> > >
>>> > > It seems in late September, fedora 22 moved to fedora archives, so I
>>> > think
>>> > > we just need those URLs changed to:
>>> > >
>>> > > http://archives.fedoraproject.org/pub/archive/fedora-
>>> > > secondary/releases/22/Everything/ppc64le/
>>> > >
>>> > > I don't have the capacity to test fedora on a ppc64le machine, but it
>>> > seems
>>> > > like simple fix on paper ;)
>>> > >
>>> > > -Kevin
>>> > >
>>> > > On Sun, Oct 8, 2017 at 3:29 PM, Evans Ye <ev...@apache.org> wrote:
>>> > >
>>> > > > Okay, heading down the path to 1.2.1 release.
>>> > > > I'm on the journey to prepare the repos on S3...
>>> > > >
>>> > > > PROGRESS
>>> > > > [V] Build 1.2.1 Docker slave images
>>> > > > [V] Build 1.2.1 RPM/DEB packages
>>> > > > [V] Sign packages
>>> > > > [X] Upload artifacts to S3
>>> > > > [X] Run through deployment test
>>> > > > [X] Vote for RC -> release
>>> > > >
>>> > > > Finally I'm able to produce all x86_64 artifacts:
>>> > > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1
>>> > > > (Actually I've to keep retrying to get these builds done. Don't
>>> know
>>> > why
>>> > > > sometimes entering infinite loop though...)
>>> > > > and their corresponding signed repos for S3 uploading.
>>> > > >
>>> > > > However, I got some problems with PPC64LE.
>>> > > > We can build arch independent artifacts on other machines for
>>> sure, but
>>> > > > hadoop,
>>> > > > qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines.
>>> And
>>> > > that
>>> > > > is currently failing on ubuntu 16.04:
>>> > > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-
>>> ppc64le/
>>> > > >
>>> > > > At a glance I guess something need to be fixed for PPC docker
>>> slaves
>>> > > image.
>>> > > > I can give it a look, but if some one can help it would be
>>> appreciated.
>>> > > > It is indeed tons of work for getting a release out ;)
>>> > > >
>>> > > >
>>> > > > 2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>>> > > >
>>> > > > > Hi,
>>> > > > >
>>> > > > > The failure of gpdb looks like a serious problem to me, see
>>> > BIGTOP-2901
>>> > > > > I am too for an +1 to disable this for 1.2.1
>>> > > > >
>>> > > > > Thank you Evans for being still on track to release.
>>> > > > >
>>> > > > > Olaf
>>> > > > >
>>> > > > >
>>> > > > > > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <
>>> cos@apache.org
>>> > >:
>>> > > > > >
>>> > > > > > Well, if we can't fix it - let's nuke it. +1
>>> > > > > > --
>>> > > > > > With regards,
>>> > > > > > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org>
>>> > > wrote:
>>> > > > > >> Thanks Olaf!
>>> > > > > >> I see all the slaves images are now back to normal.
>>> > > > > >>
>>> > > > > >> I'll have a national holiday tomorrow and I'd like to spend
>>> it on
>>> > > > Bigtop
>>> > > > > >> 1.2.1 release.
>>> > > > > >> Right now, we're blocked by two issues:
>>> > > > > >>
>>> > > > > >> Crunch build failed: https://issues.apache.org/
>>> > > > jira/browse/BIGTOP-2900
>>> > > > > >> GPDB build failed: https://issues.apache.org/
>>> > > jira/browse/BIGTOP-2901
>>> > > > > >>
>>> > > > > >> I've provided a workaround patch in BIGTOP-2900, however I
>>> have
>>> > > > > completely
>>> > > > > >> no idea for BIGTOP-2901.
>>> > > > > >> Since I've raised the problem few days ago, if no one has
>>> time to
>>> > > fix
>>> > > > > it,
>>> > > > > >> I'd like to propose to disable GPDB in 1.2.1 release.
>>> > > > > >> That means in 1.2.1 release there is no GPDB binary artifact
>>> > > > available,
>>> > > > > but
>>> > > > > >> we can still refine GPDB's quality in the master branch.
>>> > > > > >>
>>> > > > > >> How do you think?
>>> > > > > >>
>>> > > > > >>
>>> > > > > >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
>>> > > > > >>
>>> > > > > >>> Let me take a look today
>>> > > > > >>>
>>> > > > > >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <
>>> > > cos@apache.org>
>>> > > > > >>> wrote:
>>> > > > > >>>> Explicitly adding Rvs in the loop
>>> > > > > >>>> --
>>> > > > > >>>> With regards,
>>> > > > > >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <
>>> evansye@apache.org>
>>> > > > > wrote:
>>> > > > > >>>>> Hi Bigtoper,
>>> > > > > >>>>>
>>> > > > > >>>>> I'm working on the 1.2.1 release. Hopefully we can get it
>>> to
>>> > the
>>> > > > > finish
>>> > > > > >>>>> line by the end on Sept.
>>> > > > > >>>>>
>>> > > > > >>>>> Right now we still have a few issues blocking:
>>> > > > > >>>>>
>>> > > > > >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
>>> > > > > >>>>> 2. Toolchain build failed on PPC64LE platform[2]
>>> > > > > >>>>>
>>> > > > > >>>>> I'll update more down the path. But right now I'd like to
>>> seek
>>> > > for
>>> > > > > some
>>> > > > > >>>>> helps on GPDB and PPC64LE side ;)
>>> > > > > >>>>>
>>> > > > > >>>>>
>>> > > > > >>>>> [1]. https://ci.bigtop.apache.org/v
>>> iew/Releases/job/Bigtop-1.2
>>> > .
>>> > > 1/
>>> > > > > >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
>>> > > > > >>> Toolchain-1.2.1/
>>> > > > > >>>>>
>>> > > > > >>>>>
>>> > > > > >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>>> > > > > >>>>>
>>> > > > > >>>>>> Thanks, Arnaud
>>> > > > > >>>>>>
>>> > > > > >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>>> > > > > >>>>>> bigtop/slaves:1.2.1-$OS bash -l
>>> > > > > >>>>>> root@596ef2c638de:/# java -version
>>> > > > > >>>>>> openjdk version "1.8.0_131"
>>> > > > > >>>>>> OpenJDK Runtime Environment (build
>>> > 1.8.0_131-8u131-b11-0ubuntu1.
>>> > > > > >>>>>> 16.04.2-b11)
>>> > > > > >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>>> > > > > >>>>>>
>>> > > > > >>>>>> Looks linked!
>>> > > > > >>>>>>
>>> > > > > >>>>>>
>>> > > > > >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>>> > > > > >>>>>>
>>> > > > > >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a
>>> écrit:
>>> > > > > >>>>>>>> 1. Somehow packages on centos and debian changed. If we
>>> > > rebuild
>>> > > > > >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as
>>> > what
>>> > > we
>>> > > > > >>> faced
>>> > > > > >>>>>>>> building with 1.2.1 images.
>>> > > > > >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
>>> > > > > >>>>>>>> Any thoughts?
>>> > > > > >>>>>>>
>>> > > > > >>>>>>> Check the java version, somehow the java docs whatever
>>> stuff
>>> > > > > >>>>>>> changed in 8.131, and solr doesn't compile anymore with
>>> java8
>>> > > > > >=131 .
>>> > > > > >>>>>>> Might be linked.
>>> > > > > >>>>>>>
>>> > > > > >>>>>>> Arnaud.
>>> > > > > >>>>>>>
>>> > > > > >>>>>>
>>> > > > > >>>>>>
>>> > > > > >>>
>>> > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
>>>
>>
>>
>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
More test have been done for 1.2.1 release.
https://ci.bigtop.apache.org/job/Bigtop-1.2.1-installation
This job tests whether packages can be installed cleanly with pgp
verification
Though not all the packages can be successfully installed due to conflicts,
most of them are good.
Following are packages failed to install:
CentOS, Fedora:
qfs-python.x86_64
OpenSuSE:
Hue, Oozie
Debian, Ubuntu:
Hue, Oozie, Phoenix, QFS
2017-10-13 3:39 GMT+08:00 Evans Ye <ev...@apache.org>:
> AFAIK, the build slave for arm is offline in our CI:
>
> docker-slave-arm-1
> <https://ci.bigtop.apache.org/computer/docker-slave-arm-1/> (offline)
>
> If you can get it back into business, then there's no reason not to
> include it as long as it's in good shape.
>
> 2017-10-13 3:31 GMT+08:00 Ganesh Raju <ga...@linaro.org>:
>
>> Evans
>>
>> What is needed to reestablish the CI builds for Aarch? We are ready to
>> help
>> that getting setup as well
>> We have setup CI builds internally in Linaro which has been working fine.
>>
>> Do you need access to the two arm systems for builds?
>>
>>
>> Thanks,
>> Ganesh
>>
>> On Thu, Oct 12, 2017 at 1:56 PM, Evans Ye <ev...@apache.org> wrote:
>>
>> > Thanks Kevin for doing the investigation. That is addressed in
>> BIGTOP-2904.
>> >
>> > Regarding to 1.2.1 release. I've finally crossed the finish line and
>> have
>> > put it up for a vote.
>> > Let me share some of the details here:
>> >
>> > * All the signed repos are on repos.bigtop.apache.org, which is backed
>> by
>> > our new S3 directory
>> > * Deployment evaluated by
>> > https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-1.
>> > 2.1-deployments/,
>> > which installs packages from repos.bigtop.apache.org. Surely we've some
>> > red
>> > dots, but those problems are also in 1.2.0 as well. 1.2.1 actually
>> > improves/fixes things that was broken in 1.2.0.
>> > * Binary convenient artifacts are not available for PPC64LE, but we can
>> > still put them up afterwards.
>> >
>> > Thanks for everyone who helped making this release happening.
>> > The release stuffs are in the [VOTE] mailing thread. If you've time.
>> Please
>> > give it try and provide your feedback.
>> >
>> >
>> > Evans
>> >
>> >
>> >
>> > 2017-10-10 2:02 GMT+08:00 Kevin Monroe <ke...@canonical.com>:
>> >
>> > > Hey Evans, ubuntu 16.04 seems ok from your CI link, but fedora 25 has
>> a
>> > > problem:
>> > >
>> > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1-ppc64le/OS=
>> > > fedora-25-ppc64le/lastFailedBuild/console
>> > >
>> > > I *think* I've tracked this down to the location of protobuf. Note
>> the
>> > URL
>> > > for rpm-based ppc64le distros:
>> > >
>> > > https://github.com/apache/bigtop/blob/master/bigtop_
>> > > toolchain/manifests/protobuf.pp#L54
>> > >
>> > > Those fedora-22 URLs are no longer valid:
>> > >
>> > > https://dl.fedoraproject.org/pub/fedora-secondary/releases/
>> > > 22/Everything/ppc64le/
>> > >
>> > > It seems in late September, fedora 22 moved to fedora archives, so I
>> > think
>> > > we just need those URLs changed to:
>> > >
>> > > http://archives.fedoraproject.org/pub/archive/fedora-
>> > > secondary/releases/22/Everything/ppc64le/
>> > >
>> > > I don't have the capacity to test fedora on a ppc64le machine, but it
>> > seems
>> > > like simple fix on paper ;)
>> > >
>> > > -Kevin
>> > >
>> > > On Sun, Oct 8, 2017 at 3:29 PM, Evans Ye <ev...@apache.org> wrote:
>> > >
>> > > > Okay, heading down the path to 1.2.1 release.
>> > > > I'm on the journey to prepare the repos on S3...
>> > > >
>> > > > PROGRESS
>> > > > [V] Build 1.2.1 Docker slave images
>> > > > [V] Build 1.2.1 RPM/DEB packages
>> > > > [V] Sign packages
>> > > > [X] Upload artifacts to S3
>> > > > [X] Run through deployment test
>> > > > [X] Vote for RC -> release
>> > > >
>> > > > Finally I'm able to produce all x86_64 artifacts:
>> > > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1
>> > > > (Actually I've to keep retrying to get these builds done. Don't know
>> > why
>> > > > sometimes entering infinite loop though...)
>> > > > and their corresponding signed repos for S3 uploading.
>> > > >
>> > > > However, I got some problems with PPC64LE.
>> > > > We can build arch independent artifacts on other machines for sure,
>> but
>> > > > hadoop,
>> > > > qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines.
>> And
>> > > that
>> > > > is currently failing on ubuntu 16.04:
>> > > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-
>> ppc64le/
>> > > >
>> > > > At a glance I guess something need to be fixed for PPC docker slaves
>> > > image.
>> > > > I can give it a look, but if some one can help it would be
>> appreciated.
>> > > > It is indeed tons of work for getting a release out ;)
>> > > >
>> > > >
>> > > > 2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>> > > >
>> > > > > Hi,
>> > > > >
>> > > > > The failure of gpdb looks like a serious problem to me, see
>> > BIGTOP-2901
>> > > > > I am too for an +1 to disable this for 1.2.1
>> > > > >
>> > > > > Thank you Evans for being still on track to release.
>> > > > >
>> > > > > Olaf
>> > > > >
>> > > > >
>> > > > > > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <
>> cos@apache.org
>> > >:
>> > > > > >
>> > > > > > Well, if we can't fix it - let's nuke it. +1
>> > > > > > --
>> > > > > > With regards,
>> > > > > > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org>
>> > > wrote:
>> > > > > >> Thanks Olaf!
>> > > > > >> I see all the slaves images are now back to normal.
>> > > > > >>
>> > > > > >> I'll have a national holiday tomorrow and I'd like to spend it
>> on
>> > > > Bigtop
>> > > > > >> 1.2.1 release.
>> > > > > >> Right now, we're blocked by two issues:
>> > > > > >>
>> > > > > >> Crunch build failed: https://issues.apache.org/
>> > > > jira/browse/BIGTOP-2900
>> > > > > >> GPDB build failed: https://issues.apache.org/
>> > > jira/browse/BIGTOP-2901
>> > > > > >>
>> > > > > >> I've provided a workaround patch in BIGTOP-2900, however I have
>> > > > > completely
>> > > > > >> no idea for BIGTOP-2901.
>> > > > > >> Since I've raised the problem few days ago, if no one has time
>> to
>> > > fix
>> > > > > it,
>> > > > > >> I'd like to propose to disable GPDB in 1.2.1 release.
>> > > > > >> That means in 1.2.1 release there is no GPDB binary artifact
>> > > > available,
>> > > > > but
>> > > > > >> we can still refine GPDB's quality in the master branch.
>> > > > > >>
>> > > > > >> How do you think?
>> > > > > >>
>> > > > > >>
>> > > > > >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
>> > > > > >>
>> > > > > >>> Let me take a look today
>> > > > > >>>
>> > > > > >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <
>> > > cos@apache.org>
>> > > > > >>> wrote:
>> > > > > >>>> Explicitly adding Rvs in the loop
>> > > > > >>>> --
>> > > > > >>>> With regards,
>> > > > > >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <
>> evansye@apache.org>
>> > > > > wrote:
>> > > > > >>>>> Hi Bigtoper,
>> > > > > >>>>>
>> > > > > >>>>> I'm working on the 1.2.1 release. Hopefully we can get it to
>> > the
>> > > > > finish
>> > > > > >>>>> line by the end on Sept.
>> > > > > >>>>>
>> > > > > >>>>> Right now we still have a few issues blocking:
>> > > > > >>>>>
>> > > > > >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
>> > > > > >>>>> 2. Toolchain build failed on PPC64LE platform[2]
>> > > > > >>>>>
>> > > > > >>>>> I'll update more down the path. But right now I'd like to
>> seek
>> > > for
>> > > > > some
>> > > > > >>>>> helps on GPDB and PPC64LE side ;)
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>> [1]. https://ci.bigtop.apache.org/v
>> iew/Releases/job/Bigtop-1.2
>> > .
>> > > 1/
>> > > > > >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
>> > > > > >>> Toolchain-1.2.1/
>> > > > > >>>>>
>> > > > > >>>>>
>> > > > > >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>> > > > > >>>>>
>> > > > > >>>>>> Thanks, Arnaud
>> > > > > >>>>>>
>> > > > > >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>> > > > > >>>>>> bigtop/slaves:1.2.1-$OS bash -l
>> > > > > >>>>>> root@596ef2c638de:/# java -version
>> > > > > >>>>>> openjdk version "1.8.0_131"
>> > > > > >>>>>> OpenJDK Runtime Environment (build
>> > 1.8.0_131-8u131-b11-0ubuntu1.
>> > > > > >>>>>> 16.04.2-b11)
>> > > > > >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>> > > > > >>>>>>
>> > > > > >>>>>> Looks linked!
>> > > > > >>>>>>
>> > > > > >>>>>>
>> > > > > >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>> > > > > >>>>>>
>> > > > > >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a
>> écrit:
>> > > > > >>>>>>>> 1. Somehow packages on centos and debian changed. If we
>> > > rebuild
>> > > > > >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as
>> > what
>> > > we
>> > > > > >>> faced
>> > > > > >>>>>>>> building with 1.2.1 images.
>> > > > > >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
>> > > > > >>>>>>>> Any thoughts?
>> > > > > >>>>>>>
>> > > > > >>>>>>> Check the java version, somehow the java docs whatever
>> stuff
>> > > > > >>>>>>> changed in 8.131, and solr doesn't compile anymore with
>> java8
>> > > > > >=131 .
>> > > > > >>>>>>> Might be linked.
>> > > > > >>>>>>>
>> > > > > >>>>>>> Arnaud.
>> > > > > >>>>>>>
>> > > > > >>>>>>
>> > > > > >>>>>>
>> > > > > >>>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>>
>>
>> --
>> IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
>>
>
>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
AFAIK, the build slave for arm is offline in our CI:
docker-slave-arm-1
<https://ci.bigtop.apache.org/computer/docker-slave-arm-1/> (offline)
If you can get it back into business, then there's no reason not to include
it as long as it's in good shape.
2017-10-13 3:31 GMT+08:00 Ganesh Raju <ga...@linaro.org>:
> Evans
>
> What is needed to reestablish the CI builds for Aarch? We are ready to help
> that getting setup as well
> We have setup CI builds internally in Linaro which has been working fine.
>
> Do you need access to the two arm systems for builds?
>
>
> Thanks,
> Ganesh
>
> On Thu, Oct 12, 2017 at 1:56 PM, Evans Ye <ev...@apache.org> wrote:
>
> > Thanks Kevin for doing the investigation. That is addressed in
> BIGTOP-2904.
> >
> > Regarding to 1.2.1 release. I've finally crossed the finish line and have
> > put it up for a vote.
> > Let me share some of the details here:
> >
> > * All the signed repos are on repos.bigtop.apache.org, which is backed
> by
> > our new S3 directory
> > * Deployment evaluated by
> > https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-1.
> > 2.1-deployments/,
> > which installs packages from repos.bigtop.apache.org. Surely we've some
> > red
> > dots, but those problems are also in 1.2.0 as well. 1.2.1 actually
> > improves/fixes things that was broken in 1.2.0.
> > * Binary convenient artifacts are not available for PPC64LE, but we can
> > still put them up afterwards.
> >
> > Thanks for everyone who helped making this release happening.
> > The release stuffs are in the [VOTE] mailing thread. If you've time.
> Please
> > give it try and provide your feedback.
> >
> >
> > Evans
> >
> >
> >
> > 2017-10-10 2:02 GMT+08:00 Kevin Monroe <ke...@canonical.com>:
> >
> > > Hey Evans, ubuntu 16.04 seems ok from your CI link, but fedora 25 has a
> > > problem:
> > >
> > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1-ppc64le/OS=
> > > fedora-25-ppc64le/lastFailedBuild/console
> > >
> > > I *think* I've tracked this down to the location of protobuf. Note the
> > URL
> > > for rpm-based ppc64le distros:
> > >
> > > https://github.com/apache/bigtop/blob/master/bigtop_
> > > toolchain/manifests/protobuf.pp#L54
> > >
> > > Those fedora-22 URLs are no longer valid:
> > >
> > > https://dl.fedoraproject.org/pub/fedora-secondary/releases/
> > > 22/Everything/ppc64le/
> > >
> > > It seems in late September, fedora 22 moved to fedora archives, so I
> > think
> > > we just need those URLs changed to:
> > >
> > > http://archives.fedoraproject.org/pub/archive/fedora-
> > > secondary/releases/22/Everything/ppc64le/
> > >
> > > I don't have the capacity to test fedora on a ppc64le machine, but it
> > seems
> > > like simple fix on paper ;)
> > >
> > > -Kevin
> > >
> > > On Sun, Oct 8, 2017 at 3:29 PM, Evans Ye <ev...@apache.org> wrote:
> > >
> > > > Okay, heading down the path to 1.2.1 release.
> > > > I'm on the journey to prepare the repos on S3...
> > > >
> > > > PROGRESS
> > > > [V] Build 1.2.1 Docker slave images
> > > > [V] Build 1.2.1 RPM/DEB packages
> > > > [V] Sign packages
> > > > [X] Upload artifacts to S3
> > > > [X] Run through deployment test
> > > > [X] Vote for RC -> release
> > > >
> > > > Finally I'm able to produce all x86_64 artifacts:
> > > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1
> > > > (Actually I've to keep retrying to get these builds done. Don't know
> > why
> > > > sometimes entering infinite loop though...)
> > > > and their corresponding signed repos for S3 uploading.
> > > >
> > > > However, I got some problems with PPC64LE.
> > > > We can build arch independent artifacts on other machines for sure,
> but
> > > > hadoop,
> > > > qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines.
> And
> > > that
> > > > is currently failing on ubuntu 16.04:
> > > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-ppc64le/
> > > >
> > > > At a glance I guess something need to be fixed for PPC docker slaves
> > > image.
> > > > I can give it a look, but if some one can help it would be
> appreciated.
> > > > It is indeed tons of work for getting a release out ;)
> > > >
> > > >
> > > > 2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> > > >
> > > > > Hi,
> > > > >
> > > > > The failure of gpdb looks like a serious problem to me, see
> > BIGTOP-2901
> > > > > I am too for an +1 to disable this for 1.2.1
> > > > >
> > > > > Thank you Evans for being still on track to release.
> > > > >
> > > > > Olaf
> > > > >
> > > > >
> > > > > > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <
> cos@apache.org
> > >:
> > > > > >
> > > > > > Well, if we can't fix it - let's nuke it. +1
> > > > > > --
> > > > > > With regards,
> > > > > > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org>
> > > wrote:
> > > > > >> Thanks Olaf!
> > > > > >> I see all the slaves images are now back to normal.
> > > > > >>
> > > > > >> I'll have a national holiday tomorrow and I'd like to spend it
> on
> > > > Bigtop
> > > > > >> 1.2.1 release.
> > > > > >> Right now, we're blocked by two issues:
> > > > > >>
> > > > > >> Crunch build failed: https://issues.apache.org/
> > > > jira/browse/BIGTOP-2900
> > > > > >> GPDB build failed: https://issues.apache.org/
> > > jira/browse/BIGTOP-2901
> > > > > >>
> > > > > >> I've provided a workaround patch in BIGTOP-2900, however I have
> > > > > completely
> > > > > >> no idea for BIGTOP-2901.
> > > > > >> Since I've raised the problem few days ago, if no one has time
> to
> > > fix
> > > > > it,
> > > > > >> I'd like to propose to disable GPDB in 1.2.1 release.
> > > > > >> That means in 1.2.1 release there is no GPDB binary artifact
> > > > available,
> > > > > but
> > > > > >> we can still refine GPDB's quality in the master branch.
> > > > > >>
> > > > > >> How do you think?
> > > > > >>
> > > > > >>
> > > > > >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
> > > > > >>
> > > > > >>> Let me take a look today
> > > > > >>>
> > > > > >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <
> > > cos@apache.org>
> > > > > >>> wrote:
> > > > > >>>> Explicitly adding Rvs in the loop
> > > > > >>>> --
> > > > > >>>> With regards,
> > > > > >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <
> evansye@apache.org>
> > > > > wrote:
> > > > > >>>>> Hi Bigtoper,
> > > > > >>>>>
> > > > > >>>>> I'm working on the 1.2.1 release. Hopefully we can get it to
> > the
> > > > > finish
> > > > > >>>>> line by the end on Sept.
> > > > > >>>>>
> > > > > >>>>> Right now we still have a few issues blocking:
> > > > > >>>>>
> > > > > >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
> > > > > >>>>> 2. Toolchain build failed on PPC64LE platform[2]
> > > > > >>>>>
> > > > > >>>>> I'll update more down the path. But right now I'd like to
> seek
> > > for
> > > > > some
> > > > > >>>>> helps on GPDB and PPC64LE side ;)
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> [1]. https://ci.bigtop.apache.org/
> view/Releases/job/Bigtop-1.2
> > .
> > > 1/
> > > > > >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
> > > > > >>> Toolchain-1.2.1/
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> > > > > >>>>>
> > > > > >>>>>> Thanks, Arnaud
> > > > > >>>>>>
> > > > > >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> > > > > >>>>>> bigtop/slaves:1.2.1-$OS bash -l
> > > > > >>>>>> root@596ef2c638de:/# java -version
> > > > > >>>>>> openjdk version "1.8.0_131"
> > > > > >>>>>> OpenJDK Runtime Environment (build
> > 1.8.0_131-8u131-b11-0ubuntu1.
> > > > > >>>>>> 16.04.2-b11)
> > > > > >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> > > > > >>>>>>
> > > > > >>>>>> Looks linked!
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> > > > > >>>>>>
> > > > > >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> > > > > >>>>>>>> 1. Somehow packages on centos and debian changed. If we
> > > rebuild
> > > > > >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as
> > what
> > > we
> > > > > >>> faced
> > > > > >>>>>>>> building with 1.2.1 images.
> > > > > >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
> > > > > >>>>>>>> Any thoughts?
> > > > > >>>>>>>
> > > > > >>>>>>> Check the java version, somehow the java docs whatever
> stuff
> > > > > >>>>>>> changed in 8.131, and solr doesn't compile anymore with
> java8
> > > > > >=131 .
> > > > > >>>>>>> Might be linked.
> > > > > >>>>>>>
> > > > > >>>>>>> Arnaud.
> > > > > >>>>>>>
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>
> > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
>
Re: Releasing 1.2.1
Posted by Ganesh Raju <ga...@linaro.org>.
Evans
What is needed to reestablish the CI builds for Aarch? We are ready to help
that getting setup as well
We have setup CI builds internally in Linaro which has been working fine.
Do you need access to the two arm systems for builds?
Thanks,
Ganesh
On Thu, Oct 12, 2017 at 1:56 PM, Evans Ye <ev...@apache.org> wrote:
> Thanks Kevin for doing the investigation. That is addressed in BIGTOP-2904.
>
> Regarding to 1.2.1 release. I've finally crossed the finish line and have
> put it up for a vote.
> Let me share some of the details here:
>
> * All the signed repos are on repos.bigtop.apache.org, which is backed by
> our new S3 directory
> * Deployment evaluated by
> https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-1.
> 2.1-deployments/,
> which installs packages from repos.bigtop.apache.org. Surely we've some
> red
> dots, but those problems are also in 1.2.0 as well. 1.2.1 actually
> improves/fixes things that was broken in 1.2.0.
> * Binary convenient artifacts are not available for PPC64LE, but we can
> still put them up afterwards.
>
> Thanks for everyone who helped making this release happening.
> The release stuffs are in the [VOTE] mailing thread. If you've time. Please
> give it try and provide your feedback.
>
>
> Evans
>
>
>
> 2017-10-10 2:02 GMT+08:00 Kevin Monroe <ke...@canonical.com>:
>
> > Hey Evans, ubuntu 16.04 seems ok from your CI link, but fedora 25 has a
> > problem:
> >
> > https://ci.bigtop.apache.org/job/Bigtop-1.2.1-ppc64le/OS=
> > fedora-25-ppc64le/lastFailedBuild/console
> >
> > I *think* I've tracked this down to the location of protobuf. Note the
> URL
> > for rpm-based ppc64le distros:
> >
> > https://github.com/apache/bigtop/blob/master/bigtop_
> > toolchain/manifests/protobuf.pp#L54
> >
> > Those fedora-22 URLs are no longer valid:
> >
> > https://dl.fedoraproject.org/pub/fedora-secondary/releases/
> > 22/Everything/ppc64le/
> >
> > It seems in late September, fedora 22 moved to fedora archives, so I
> think
> > we just need those URLs changed to:
> >
> > http://archives.fedoraproject.org/pub/archive/fedora-
> > secondary/releases/22/Everything/ppc64le/
> >
> > I don't have the capacity to test fedora on a ppc64le machine, but it
> seems
> > like simple fix on paper ;)
> >
> > -Kevin
> >
> > On Sun, Oct 8, 2017 at 3:29 PM, Evans Ye <ev...@apache.org> wrote:
> >
> > > Okay, heading down the path to 1.2.1 release.
> > > I'm on the journey to prepare the repos on S3...
> > >
> > > PROGRESS
> > > [V] Build 1.2.1 Docker slave images
> > > [V] Build 1.2.1 RPM/DEB packages
> > > [V] Sign packages
> > > [X] Upload artifacts to S3
> > > [X] Run through deployment test
> > > [X] Vote for RC -> release
> > >
> > > Finally I'm able to produce all x86_64 artifacts:
> > > https://ci.bigtop.apache.org/job/Bigtop-1.2.1
> > > (Actually I've to keep retrying to get these builds done. Don't know
> why
> > > sometimes entering infinite loop though...)
> > > and their corresponding signed repos for S3 uploading.
> > >
> > > However, I got some problems with PPC64LE.
> > > We can build arch independent artifacts on other machines for sure, but
> > > hadoop,
> > > qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines. And
> > that
> > > is currently failing on ubuntu 16.04:
> > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-ppc64le/
> > >
> > > At a glance I guess something need to be fixed for PPC docker slaves
> > image.
> > > I can give it a look, but if some one can help it would be appreciated.
> > > It is indeed tons of work for getting a release out ;)
> > >
> > >
> > > 2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> > >
> > > > Hi,
> > > >
> > > > The failure of gpdb looks like a serious problem to me, see
> BIGTOP-2901
> > > > I am too for an +1 to disable this for 1.2.1
> > > >
> > > > Thank you Evans for being still on track to release.
> > > >
> > > > Olaf
> > > >
> > > >
> > > > > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <cos@apache.org
> >:
> > > > >
> > > > > Well, if we can't fix it - let's nuke it. +1
> > > > > --
> > > > > With regards,
> > > > > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org>
> > wrote:
> > > > >> Thanks Olaf!
> > > > >> I see all the slaves images are now back to normal.
> > > > >>
> > > > >> I'll have a national holiday tomorrow and I'd like to spend it on
> > > Bigtop
> > > > >> 1.2.1 release.
> > > > >> Right now, we're blocked by two issues:
> > > > >>
> > > > >> Crunch build failed: https://issues.apache.org/
> > > jira/browse/BIGTOP-2900
> > > > >> GPDB build failed: https://issues.apache.org/
> > jira/browse/BIGTOP-2901
> > > > >>
> > > > >> I've provided a workaround patch in BIGTOP-2900, however I have
> > > > completely
> > > > >> no idea for BIGTOP-2901.
> > > > >> Since I've raised the problem few days ago, if no one has time to
> > fix
> > > > it,
> > > > >> I'd like to propose to disable GPDB in 1.2.1 release.
> > > > >> That means in 1.2.1 release there is no GPDB binary artifact
> > > available,
> > > > but
> > > > >> we can still refine GPDB's quality in the master branch.
> > > > >>
> > > > >> How do you think?
> > > > >>
> > > > >>
> > > > >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
> > > > >>
> > > > >>> Let me take a look today
> > > > >>>
> > > > >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <
> > cos@apache.org>
> > > > >>> wrote:
> > > > >>>> Explicitly adding Rvs in the loop
> > > > >>>> --
> > > > >>>> With regards,
> > > > >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org>
> > > > wrote:
> > > > >>>>> Hi Bigtoper,
> > > > >>>>>
> > > > >>>>> I'm working on the 1.2.1 release. Hopefully we can get it to
> the
> > > > finish
> > > > >>>>> line by the end on Sept.
> > > > >>>>>
> > > > >>>>> Right now we still have a few issues blocking:
> > > > >>>>>
> > > > >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
> > > > >>>>> 2. Toolchain build failed on PPC64LE platform[2]
> > > > >>>>>
> > > > >>>>> I'll update more down the path. But right now I'd like to seek
> > for
> > > > some
> > > > >>>>> helps on GPDB and PPC64LE side ;)
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2
> .
> > 1/
> > > > >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
> > > > >>> Toolchain-1.2.1/
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> > > > >>>>>
> > > > >>>>>> Thanks, Arnaud
> > > > >>>>>>
> > > > >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> > > > >>>>>> bigtop/slaves:1.2.1-$OS bash -l
> > > > >>>>>> root@596ef2c638de:/# java -version
> > > > >>>>>> openjdk version "1.8.0_131"
> > > > >>>>>> OpenJDK Runtime Environment (build
> 1.8.0_131-8u131-b11-0ubuntu1.
> > > > >>>>>> 16.04.2-b11)
> > > > >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> > > > >>>>>>
> > > > >>>>>> Looks linked!
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> > > > >>>>>>
> > > > >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> > > > >>>>>>>> 1. Somehow packages on centos and debian changed. If we
> > rebuild
> > > > >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as
> what
> > we
> > > > >>> faced
> > > > >>>>>>>> building with 1.2.1 images.
> > > > >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
> > > > >>>>>>>> Any thoughts?
> > > > >>>>>>>
> > > > >>>>>>> Check the java version, somehow the java docs whatever stuff
> > > > >>>>>>> changed in 8.131, and solr doesn't compile anymore with java8
> > > > >=131 .
> > > > >>>>>>> Might be linked.
> > > > >>>>>>>
> > > > >>>>>>> Arnaud.
> > > > >>>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>
> > > >
> > > >
> > >
> >
>
--
IRC: ganeshraju@#linaro on irc.freenode.ne <http://irc.freenode.net/>t
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Thanks Kevin for doing the investigation. That is addressed in BIGTOP-2904.
Regarding to 1.2.1 release. I've finally crossed the finish line and have
put it up for a vote.
Let me share some of the details here:
* All the signed repos are on repos.bigtop.apache.org, which is backed by
our new S3 directory
* Deployment evaluated by
https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-1.2.1-deployments/,
which installs packages from repos.bigtop.apache.org. Surely we've some red
dots, but those problems are also in 1.2.0 as well. 1.2.1 actually
improves/fixes things that was broken in 1.2.0.
* Binary convenient artifacts are not available for PPC64LE, but we can
still put them up afterwards.
Thanks for everyone who helped making this release happening.
The release stuffs are in the [VOTE] mailing thread. If you've time. Please
give it try and provide your feedback.
Evans
2017-10-10 2:02 GMT+08:00 Kevin Monroe <ke...@canonical.com>:
> Hey Evans, ubuntu 16.04 seems ok from your CI link, but fedora 25 has a
> problem:
>
> https://ci.bigtop.apache.org/job/Bigtop-1.2.1-ppc64le/OS=
> fedora-25-ppc64le/lastFailedBuild/console
>
> I *think* I've tracked this down to the location of protobuf. Note the URL
> for rpm-based ppc64le distros:
>
> https://github.com/apache/bigtop/blob/master/bigtop_
> toolchain/manifests/protobuf.pp#L54
>
> Those fedora-22 URLs are no longer valid:
>
> https://dl.fedoraproject.org/pub/fedora-secondary/releases/
> 22/Everything/ppc64le/
>
> It seems in late September, fedora 22 moved to fedora archives, so I think
> we just need those URLs changed to:
>
> http://archives.fedoraproject.org/pub/archive/fedora-
> secondary/releases/22/Everything/ppc64le/
>
> I don't have the capacity to test fedora on a ppc64le machine, but it seems
> like simple fix on paper ;)
>
> -Kevin
>
> On Sun, Oct 8, 2017 at 3:29 PM, Evans Ye <ev...@apache.org> wrote:
>
> > Okay, heading down the path to 1.2.1 release.
> > I'm on the journey to prepare the repos on S3...
> >
> > PROGRESS
> > [V] Build 1.2.1 Docker slave images
> > [V] Build 1.2.1 RPM/DEB packages
> > [V] Sign packages
> > [X] Upload artifacts to S3
> > [X] Run through deployment test
> > [X] Vote for RC -> release
> >
> > Finally I'm able to produce all x86_64 artifacts:
> > https://ci.bigtop.apache.org/job/Bigtop-1.2.1
> > (Actually I've to keep retrying to get these builds done. Don't know why
> > sometimes entering infinite loop though...)
> > and their corresponding signed repos for S3 uploading.
> >
> > However, I got some problems with PPC64LE.
> > We can build arch independent artifacts on other machines for sure, but
> > hadoop,
> > qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines. And
> that
> > is currently failing on ubuntu 16.04:
> > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-ppc64le/
> >
> > At a glance I guess something need to be fixed for PPC docker slaves
> image.
> > I can give it a look, but if some one can help it would be appreciated.
> > It is indeed tons of work for getting a release out ;)
> >
> >
> > 2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> >
> > > Hi,
> > >
> > > The failure of gpdb looks like a serious problem to me, see BIGTOP-2901
> > > I am too for an +1 to disable this for 1.2.1
> > >
> > > Thank you Evans for being still on track to release.
> > >
> > > Olaf
> > >
> > >
> > > > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <co...@apache.org>:
> > > >
> > > > Well, if we can't fix it - let's nuke it. +1
> > > > --
> > > > With regards,
> > > > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org>
> wrote:
> > > >> Thanks Olaf!
> > > >> I see all the slaves images are now back to normal.
> > > >>
> > > >> I'll have a national holiday tomorrow and I'd like to spend it on
> > Bigtop
> > > >> 1.2.1 release.
> > > >> Right now, we're blocked by two issues:
> > > >>
> > > >> Crunch build failed: https://issues.apache.org/
> > jira/browse/BIGTOP-2900
> > > >> GPDB build failed: https://issues.apache.org/
> jira/browse/BIGTOP-2901
> > > >>
> > > >> I've provided a workaround patch in BIGTOP-2900, however I have
> > > completely
> > > >> no idea for BIGTOP-2901.
> > > >> Since I've raised the problem few days ago, if no one has time to
> fix
> > > it,
> > > >> I'd like to propose to disable GPDB in 1.2.1 release.
> > > >> That means in 1.2.1 release there is no GPDB binary artifact
> > available,
> > > but
> > > >> we can still refine GPDB's quality in the master branch.
> > > >>
> > > >> How do you think?
> > > >>
> > > >>
> > > >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
> > > >>
> > > >>> Let me take a look today
> > > >>>
> > > >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <
> cos@apache.org>
> > > >>> wrote:
> > > >>>> Explicitly adding Rvs in the loop
> > > >>>> --
> > > >>>> With regards,
> > > >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org>
> > > wrote:
> > > >>>>> Hi Bigtoper,
> > > >>>>>
> > > >>>>> I'm working on the 1.2.1 release. Hopefully we can get it to the
> > > finish
> > > >>>>> line by the end on Sept.
> > > >>>>>
> > > >>>>> Right now we still have a few issues blocking:
> > > >>>>>
> > > >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
> > > >>>>> 2. Toolchain build failed on PPC64LE platform[2]
> > > >>>>>
> > > >>>>> I'll update more down the path. But right now I'd like to seek
> for
> > > some
> > > >>>>> helps on GPDB and PPC64LE side ;)
> > > >>>>>
> > > >>>>>
> > > >>>>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.
> 1/
> > > >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
> > > >>> Toolchain-1.2.1/
> > > >>>>>
> > > >>>>>
> > > >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> > > >>>>>
> > > >>>>>> Thanks, Arnaud
> > > >>>>>>
> > > >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> > > >>>>>> bigtop/slaves:1.2.1-$OS bash -l
> > > >>>>>> root@596ef2c638de:/# java -version
> > > >>>>>> openjdk version "1.8.0_131"
> > > >>>>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
> > > >>>>>> 16.04.2-b11)
> > > >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> > > >>>>>>
> > > >>>>>> Looks linked!
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> > > >>>>>>
> > > >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> > > >>>>>>>> 1. Somehow packages on centos and debian changed. If we
> rebuild
> > > >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as what
> we
> > > >>> faced
> > > >>>>>>>> building with 1.2.1 images.
> > > >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
> > > >>>>>>>> Any thoughts?
> > > >>>>>>>
> > > >>>>>>> Check the java version, somehow the java docs whatever stuff
> > > >>>>>>> changed in 8.131, and solr doesn't compile anymore with java8
> > > >=131 .
> > > >>>>>>> Might be linked.
> > > >>>>>>>
> > > >>>>>>> Arnaud.
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>
> > >
> > >
> >
>
Re: Releasing 1.2.1
Posted by Kevin Monroe <ke...@canonical.com>.
Hey Evans, ubuntu 16.04 seems ok from your CI link, but fedora 25 has a
problem:
https://ci.bigtop.apache.org/job/Bigtop-1.2.1-ppc64le/OS=fedora-25-ppc64le/lastFailedBuild/console
I *think* I've tracked this down to the location of protobuf. Note the URL
for rpm-based ppc64le distros:
https://github.com/apache/bigtop/blob/master/bigtop_toolchain/manifests/protobuf.pp#L54
Those fedora-22 URLs are no longer valid:
https://dl.fedoraproject.org/pub/fedora-secondary/releases/22/Everything/ppc64le/
It seems in late September, fedora 22 moved to fedora archives, so I think
we just need those URLs changed to:
http://archives.fedoraproject.org/pub/archive/fedora-secondary/releases/22/Everything/ppc64le/
I don't have the capacity to test fedora on a ppc64le machine, but it seems
like simple fix on paper ;)
-Kevin
On Sun, Oct 8, 2017 at 3:29 PM, Evans Ye <ev...@apache.org> wrote:
> Okay, heading down the path to 1.2.1 release.
> I'm on the journey to prepare the repos on S3...
>
> PROGRESS
> [V] Build 1.2.1 Docker slave images
> [V] Build 1.2.1 RPM/DEB packages
> [V] Sign packages
> [X] Upload artifacts to S3
> [X] Run through deployment test
> [X] Vote for RC -> release
>
> Finally I'm able to produce all x86_64 artifacts:
> https://ci.bigtop.apache.org/job/Bigtop-1.2.1
> (Actually I've to keep retrying to get these builds done. Don't know why
> sometimes entering infinite loop though...)
> and their corresponding signed repos for S3 uploading.
>
> However, I got some problems with PPC64LE.
> We can build arch independent artifacts on other machines for sure, but
> hadoop,
> qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines. And that
> is currently failing on ubuntu 16.04:
> https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-ppc64le/
>
> At a glance I guess something need to be fixed for PPC docker slaves image.
> I can give it a look, but if some one can help it would be appreciated.
> It is indeed tons of work for getting a release out ;)
>
>
> 2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>
> > Hi,
> >
> > The failure of gpdb looks like a serious problem to me, see BIGTOP-2901
> > I am too for an +1 to disable this for 1.2.1
> >
> > Thank you Evans for being still on track to release.
> >
> > Olaf
> >
> >
> > > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <co...@apache.org>:
> > >
> > > Well, if we can't fix it - let's nuke it. +1
> > > --
> > > With regards,
> > > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org> wrote:
> > >> Thanks Olaf!
> > >> I see all the slaves images are now back to normal.
> > >>
> > >> I'll have a national holiday tomorrow and I'd like to spend it on
> Bigtop
> > >> 1.2.1 release.
> > >> Right now, we're blocked by two issues:
> > >>
> > >> Crunch build failed: https://issues.apache.org/
> jira/browse/BIGTOP-2900
> > >> GPDB build failed: https://issues.apache.org/jira/browse/BIGTOP-2901
> > >>
> > >> I've provided a workaround patch in BIGTOP-2900, however I have
> > completely
> > >> no idea for BIGTOP-2901.
> > >> Since I've raised the problem few days ago, if no one has time to fix
> > it,
> > >> I'd like to propose to disable GPDB in 1.2.1 release.
> > >> That means in 1.2.1 release there is no GPDB binary artifact
> available,
> > but
> > >> we can still refine GPDB's quality in the master branch.
> > >>
> > >> How do you think?
> > >>
> > >>
> > >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
> > >>
> > >>> Let me take a look today
> > >>>
> > >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <co...@apache.org>
> > >>> wrote:
> > >>>> Explicitly adding Rvs in the loop
> > >>>> --
> > >>>> With regards,
> > >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org>
> > wrote:
> > >>>>> Hi Bigtoper,
> > >>>>>
> > >>>>> I'm working on the 1.2.1 release. Hopefully we can get it to the
> > finish
> > >>>>> line by the end on Sept.
> > >>>>>
> > >>>>> Right now we still have a few issues blocking:
> > >>>>>
> > >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
> > >>>>> 2. Toolchain build failed on PPC64LE platform[2]
> > >>>>>
> > >>>>> I'll update more down the path. But right now I'd like to seek for
> > some
> > >>>>> helps on GPDB and PPC64LE side ;)
> > >>>>>
> > >>>>>
> > >>>>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> > >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
> > >>> Toolchain-1.2.1/
> > >>>>>
> > >>>>>
> > >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> > >>>>>
> > >>>>>> Thanks, Arnaud
> > >>>>>>
> > >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> > >>>>>> bigtop/slaves:1.2.1-$OS bash -l
> > >>>>>> root@596ef2c638de:/# java -version
> > >>>>>> openjdk version "1.8.0_131"
> > >>>>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
> > >>>>>> 16.04.2-b11)
> > >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> > >>>>>>
> > >>>>>> Looks linked!
> > >>>>>>
> > >>>>>>
> > >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> > >>>>>>
> > >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> > >>>>>>>> 1. Somehow packages on centos and debian changed. If we rebuild
> > >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as what we
> > >>> faced
> > >>>>>>>> building with 1.2.1 images.
> > >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
> > >>>>>>>> Any thoughts?
> > >>>>>>>
> > >>>>>>> Check the java version, somehow the java docs whatever stuff
> > >>>>>>> changed in 8.131, and solr doesn't compile anymore with java8
> > >=131 .
> > >>>>>>> Might be linked.
> > >>>>>>>
> > >>>>>>> Arnaud.
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>
> >
> >
>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Okay, heading down the path to 1.2.1 release.
I'm on the journey to prepare the repos on S3...
PROGRESS
[V] Build 1.2.1 Docker slave images
[V] Build 1.2.1 RPM/DEB packages
[V] Sign packages
[X] Upload artifacts to S3
[X] Run through deployment test
[X] Vote for RC -> release
Finally I'm able to produce all x86_64 artifacts:
https://ci.bigtop.apache.org/job/Bigtop-1.2.1
(Actually I've to keep retrying to get these builds done. Don't know why
sometimes entering infinite loop though...)
and their corresponding signed repos for S3 uploading.
However, I got some problems with PPC64LE.
We can build arch independent artifacts on other machines for sure, but hadoop,
qfs, bigtop-jsvc, zookeeper, hue need to be built on PPC machines. And that
is currently failing on ubuntu 16.04:
https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1-ppc64le/
At a glance I guess something need to be fixed for PPC docker slaves image.
I can give it a look, but if some one can help it would be appreciated.
It is indeed tons of work for getting a release out ;)
2017-10-03 23:22 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> Hi,
>
> The failure of gpdb looks like a serious problem to me, see BIGTOP-2901
> I am too for an +1 to disable this for 1.2.1
>
> Thank you Evans for being still on track to release.
>
> Olaf
>
>
> > Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <co...@apache.org>:
> >
> > Well, if we can't fix it - let's nuke it. +1
> > --
> > With regards,
> > 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org> wrote:
> >> Thanks Olaf!
> >> I see all the slaves images are now back to normal.
> >>
> >> I'll have a national holiday tomorrow and I'd like to spend it on Bigtop
> >> 1.2.1 release.
> >> Right now, we're blocked by two issues:
> >>
> >> Crunch build failed: https://issues.apache.org/jira/browse/BIGTOP-2900
> >> GPDB build failed: https://issues.apache.org/jira/browse/BIGTOP-2901
> >>
> >> I've provided a workaround patch in BIGTOP-2900, however I have
> completely
> >> no idea for BIGTOP-2901.
> >> Since I've raised the problem few days ago, if no one has time to fix
> it,
> >> I'd like to propose to disable GPDB in 1.2.1 release.
> >> That means in 1.2.1 release there is no GPDB binary artifact available,
> but
> >> we can still refine GPDB's quality in the master branch.
> >>
> >> How do you think?
> >>
> >>
> >> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
> >>
> >>> Let me take a look today
> >>>
> >>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <co...@apache.org>
> >>> wrote:
> >>>> Explicitly adding Rvs in the loop
> >>>> --
> >>>> With regards,
> >>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org>
> wrote:
> >>>>> Hi Bigtoper,
> >>>>>
> >>>>> I'm working on the 1.2.1 release. Hopefully we can get it to the
> finish
> >>>>> line by the end on Sept.
> >>>>>
> >>>>> Right now we still have a few issues blocking:
> >>>>>
> >>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
> >>>>> 2. Toolchain build failed on PPC64LE platform[2]
> >>>>>
> >>>>> I'll update more down the path. But right now I'd like to seek for
> some
> >>>>> helps on GPDB and PPC64LE side ;)
> >>>>>
> >>>>>
> >>>>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> >>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
> >>> Toolchain-1.2.1/
> >>>>>
> >>>>>
> >>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> >>>>>
> >>>>>> Thanks, Arnaud
> >>>>>>
> >>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> >>>>>> bigtop/slaves:1.2.1-$OS bash -l
> >>>>>> root@596ef2c638de:/# java -version
> >>>>>> openjdk version "1.8.0_131"
> >>>>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
> >>>>>> 16.04.2-b11)
> >>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> >>>>>>
> >>>>>> Looks linked!
> >>>>>>
> >>>>>>
> >>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> >>>>>>
> >>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> >>>>>>>> 1. Somehow packages on centos and debian changed. If we rebuild
> >>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as what we
> >>> faced
> >>>>>>>> building with 1.2.1 images.
> >>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
> >>>>>>>> Any thoughts?
> >>>>>>>
> >>>>>>> Check the java version, somehow the java docs whatever stuff
> >>>>>>> changed in 8.131, and solr doesn't compile anymore with java8
> >=131 .
> >>>>>>> Might be linked.
> >>>>>>>
> >>>>>>> Arnaud.
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>
>
>
Re: Releasing 1.2.1
Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi,
The failure of gpdb looks like a serious problem to me, see BIGTOP-2901
I am too for an +1 to disable this for 1.2.1
Thank you Evans for being still on track to release.
Olaf
> Am 03.10.2017 um 16:20 schrieb Konstantin Boudnik <co...@apache.org>:
>
> Well, if we can't fix it - let's nuke it. +1
> --
> With regards,
> 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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org> wrote:
>> Thanks Olaf!
>> I see all the slaves images are now back to normal.
>>
>> I'll have a national holiday tomorrow and I'd like to spend it on Bigtop
>> 1.2.1 release.
>> Right now, we're blocked by two issues:
>>
>> Crunch build failed: https://issues.apache.org/jira/browse/BIGTOP-2900
>> GPDB build failed: https://issues.apache.org/jira/browse/BIGTOP-2901
>>
>> I've provided a workaround patch in BIGTOP-2900, however I have completely
>> no idea for BIGTOP-2901.
>> Since I've raised the problem few days ago, if no one has time to fix it,
>> I'd like to propose to disable GPDB in 1.2.1 release.
>> That means in 1.2.1 release there is no GPDB binary artifact available, but
>> we can still refine GPDB's quality in the master branch.
>>
>> How do you think?
>>
>>
>> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
>>
>>> Let me take a look today
>>>
>>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <co...@apache.org>
>>> wrote:
>>>> Explicitly adding Rvs in the loop
>>>> --
>>>> With regards,
>>>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
>>>>> Hi Bigtoper,
>>>>>
>>>>> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
>>>>> line by the end on Sept.
>>>>>
>>>>> Right now we still have a few issues blocking:
>>>>>
>>>>> 1. GPDB build failed on OpenSuSE 42.1[1]
>>>>> 2. Toolchain build failed on PPC64LE platform[2]
>>>>>
>>>>> I'll update more down the path. But right now I'd like to seek for some
>>>>> helps on GPDB and PPC64LE side ;)
>>>>>
>>>>>
>>>>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>>>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
>>> Toolchain-1.2.1/
>>>>>
>>>>>
>>>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>>>>>
>>>>>> Thanks, Arnaud
>>>>>>
>>>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>>>>>> bigtop/slaves:1.2.1-$OS bash -l
>>>>>> root@596ef2c638de:/# java -version
>>>>>> openjdk version "1.8.0_131"
>>>>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
>>>>>> 16.04.2-b11)
>>>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>>>>>>
>>>>>> Looks linked!
>>>>>>
>>>>>>
>>>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>>>>>>
>>>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>>>>>>>> 1. Somehow packages on centos and debian changed. If we rebuild
>>>>>>>> bigtop/slaves for trunk, then Solr will fail the same as what we
>>> faced
>>>>>>>> building with 1.2.1 images.
>>>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
>>>>>>>> Any thoughts?
>>>>>>>
>>>>>>> Check the java version, somehow the java docs whatever stuff
>>>>>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>>>>>>> Might be linked.
>>>>>>>
>>>>>>> Arnaud.
>>>>>>>
>>>>>>
>>>>>>
>>>
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Well, if we can't fix it - let's nuke it. +1
--
With regards,
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 Tue, Oct 3, 2017 at 10:11 AM, Evans Ye <ev...@apache.org> wrote:
> Thanks Olaf!
> I see all the slaves images are now back to normal.
>
> I'll have a national holiday tomorrow and I'd like to spend it on Bigtop
> 1.2.1 release.
> Right now, we're blocked by two issues:
>
> Crunch build failed: https://issues.apache.org/jira/browse/BIGTOP-2900
> GPDB build failed: https://issues.apache.org/jira/browse/BIGTOP-2901
>
> I've provided a workaround patch in BIGTOP-2900, however I have completely
> no idea for BIGTOP-2901.
> Since I've raised the problem few days ago, if no one has time to fix it,
> I'd like to propose to disable GPDB in 1.2.1 release.
> That means in 1.2.1 release there is no GPDB binary artifact available, but
> we can still refine GPDB's quality in the master branch.
>
> How do you think?
>
>
> 2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
>
>> Let me take a look today
>>
>> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <co...@apache.org>
>> wrote:
>> > Explicitly adding Rvs in the loop
>> > --
>> > With regards,
>> > 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
>> >> Hi Bigtoper,
>> >>
>> >> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
>> >> line by the end on Sept.
>> >>
>> >> Right now we still have a few issues blocking:
>> >>
>> >> 1. GPDB build failed on OpenSuSE 42.1[1]
>> >> 2. Toolchain build failed on PPC64LE platform[2]
>> >>
>> >> I'll update more down the path. But right now I'd like to seek for some
>> >> helps on GPDB and PPC64LE side ;)
>> >>
>> >>
>> >> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>> >> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
>> Toolchain-1.2.1/
>> >>
>> >>
>> >> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>> >>
>> >>> Thanks, Arnaud
>> >>>
>> >>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>> >>> bigtop/slaves:1.2.1-$OS bash -l
>> >>> root@596ef2c638de:/# java -version
>> >>> openjdk version "1.8.0_131"
>> >>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
>> >>> 16.04.2-b11)
>> >>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>> >>>
>> >>> Looks linked!
>> >>>
>> >>>
>> >>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>> >>>
>> >>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>> >>>> > 1. Somehow packages on centos and debian changed. If we rebuild
>> >>>> > bigtop/slaves for trunk, then Solr will fail the same as what we
>> faced
>> >>>> > building with 1.2.1 images.
>> >>>> > 2. We've special tweaks for bigtop/slaves trunk images.
>> >>>> > Any thoughts?
>> >>>>
>> >>>> Check the java version, somehow the java docs whatever stuff
>> >>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>> >>>> Might be linked.
>> >>>>
>> >>>> Arnaud.
>> >>>>
>> >>>
>> >>>
>>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Thanks Olaf!
I see all the slaves images are now back to normal.
I'll have a national holiday tomorrow and I'd like to spend it on Bigtop
1.2.1 release.
Right now, we're blocked by two issues:
Crunch build failed: https://issues.apache.org/jira/browse/BIGTOP-2900
GPDB build failed: https://issues.apache.org/jira/browse/BIGTOP-2901
I've provided a workaround patch in BIGTOP-2900, however I have completely
no idea for BIGTOP-2901.
Since I've raised the problem few days ago, if no one has time to fix it,
I'd like to propose to disable GPDB in 1.2.1 release.
That means in 1.2.1 release there is no GPDB binary artifact available, but
we can still refine GPDB's quality in the master branch.
How do you think?
2017-09-26 5:16 GMT+08:00 Roman Shaposhnik <rv...@apache.org>:
> Let me take a look today
>
> On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <co...@apache.org>
> wrote:
> > Explicitly adding Rvs in the loop
> > --
> > With regards,
> > 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
> >> Hi Bigtoper,
> >>
> >> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
> >> line by the end on Sept.
> >>
> >> Right now we still have a few issues blocking:
> >>
> >> 1. GPDB build failed on OpenSuSE 42.1[1]
> >> 2. Toolchain build failed on PPC64LE platform[2]
> >>
> >> I'll update more down the path. But right now I'd like to seek for some
> >> helps on GPDB and PPC64LE side ;)
> >>
> >>
> >> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> >> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-
> Toolchain-1.2.1/
> >>
> >>
> >> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> >>
> >>> Thanks, Arnaud
> >>>
> >>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> >>> bigtop/slaves:1.2.1-$OS bash -l
> >>> root@596ef2c638de:/# java -version
> >>> openjdk version "1.8.0_131"
> >>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
> >>> 16.04.2-b11)
> >>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> >>>
> >>> Looks linked!
> >>>
> >>>
> >>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> >>>
> >>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> >>>> > 1. Somehow packages on centos and debian changed. If we rebuild
> >>>> > bigtop/slaves for trunk, then Solr will fail the same as what we
> faced
> >>>> > building with 1.2.1 images.
> >>>> > 2. We've special tweaks for bigtop/slaves trunk images.
> >>>> > Any thoughts?
> >>>>
> >>>> Check the java version, somehow the java docs whatever stuff
> >>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
> >>>> Might be linked.
> >>>>
> >>>> Arnaud.
> >>>>
> >>>
> >>>
>
Re: Releasing 1.2.1
Posted by Roman Shaposhnik <rv...@apache.org>.
Let me take a look today
On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik <co...@apache.org> wrote:
> Explicitly adding Rvs in the loop
> --
> With regards,
> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
>> Hi Bigtoper,
>>
>> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
>> line by the end on Sept.
>>
>> Right now we still have a few issues blocking:
>>
>> 1. GPDB build failed on OpenSuSE 42.1[1]
>> 2. Toolchain build failed on PPC64LE platform[2]
>>
>> I'll update more down the path. But right now I'd like to seek for some
>> helps on GPDB and PPC64LE side ;)
>>
>>
>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>>
>>
>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>>
>>> Thanks, Arnaud
>>>
>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>>> bigtop/slaves:1.2.1-$OS bash -l
>>> root@596ef2c638de:/# java -version
>>> openjdk version "1.8.0_131"
>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
>>> 16.04.2-b11)
>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>>>
>>> Looks linked!
>>>
>>>
>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>>>
>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>>>> > 1. Somehow packages on centos and debian changed. If we rebuild
>>>> > bigtop/slaves for trunk, then Solr will fail the same as what we faced
>>>> > building with 1.2.1 images.
>>>> > 2. We've special tweaks for bigtop/slaves trunk images.
>>>> > Any thoughts?
>>>>
>>>> Check the java version, somehow the java docs whatever stuff
>>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>>>> Might be linked.
>>>>
>>>> Arnaud.
>>>>
>>>
>>>
Re: Releasing 1.2.1
Posted by Olaf Flebbe <of...@oflebbe.de>.
Problem was the global jenkins setting https://ci.bigtop.apache.org/configureTools/ <https://ci.bigtop.apache.org/configureTools/>
JDK installation was set to "enabled" with a AMD64 JDK to be automatically installed, what surely will not work on ppc64le.
Disabled this setting. Consequence is we have to make sure every slave has a JDK installed.
I did a testrun and ubuntu and fedora on PPC64le build toolchain sucessfully. I will remove traces of these runs in the next minutes.
Started https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/11/
Olaf
> Am 24.09.2017 um 10:21 schrieb Olaf Flebbe <of...@oflebbe.de>:
>
> I think I can fix [2]
>
> Olaf
>
>> Am 23.09.2017 um 18:34 schrieb Konstantin Boudnik <co...@apache.org>:
>>
>> Explicitly adding Rvs in the loop
>> --
>> With regards,
>> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
>>> Hi Bigtoper,
>>>
>>> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
>>> line by the end on Sept.
>>>
>>> Right now we still have a few issues blocking:
>>>
>>> 1. GPDB build failed on OpenSuSE 42.1[1]
>>> 2. Toolchain build failed on PPC64LE platform[2]
>>>
>>> I'll update more down the path. But right now I'd like to seek for some
>>> helps on GPDB and PPC64LE side ;)
>>>
>>>
>>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>>>
>>>
>>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>>>
>>>> Thanks, Arnaud
>>>>
>>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>>>> bigtop/slaves:1.2.1-$OS bash -l
>>>> root@596ef2c638de:/# java -version
>>>> openjdk version "1.8.0_131"
>>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
>>>> 16.04.2-b11)
>>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>>>>
>>>> Looks linked!
>>>>
>>>>
>>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>>>>
>>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>>>>>> 1. Somehow packages on centos and debian changed. If we rebuild
>>>>>> bigtop/slaves for trunk, then Solr will fail the same as what we faced
>>>>>> building with 1.2.1 images.
>>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
>>>>>> Any thoughts?
>>>>>
>>>>> Check the java version, somehow the java docs whatever stuff
>>>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>>>>> Might be linked.
>>>>>
>>>>> Arnaud.
>>>>>
>>>>
>>>>
>
Re: Releasing 1.2.1
Posted by Olaf Flebbe <of...@oflebbe.de>.
I think I can fix [2]
Olaf
> Am 23.09.2017 um 18:34 schrieb Konstantin Boudnik <co...@apache.org>:
>
> Explicitly adding Rvs in the loop
> --
> With regards,
> 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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
>> Hi Bigtoper,
>>
>> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
>> line by the end on Sept.
>>
>> Right now we still have a few issues blocking:
>>
>> 1. GPDB build failed on OpenSuSE 42.1[1]
>> 2. Toolchain build failed on PPC64LE platform[2]
>>
>> I'll update more down the path. But right now I'd like to seek for some
>> helps on GPDB and PPC64LE side ;)
>>
>>
>> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>>
>>
>> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>>
>>> Thanks, Arnaud
>>>
>>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>>> bigtop/slaves:1.2.1-$OS bash -l
>>> root@596ef2c638de:/# java -version
>>> openjdk version "1.8.0_131"
>>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
>>> 16.04.2-b11)
>>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>>>
>>> Looks linked!
>>>
>>>
>>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>>>
>>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>>>>> 1. Somehow packages on centos and debian changed. If we rebuild
>>>>> bigtop/slaves for trunk, then Solr will fail the same as what we faced
>>>>> building with 1.2.1 images.
>>>>> 2. We've special tweaks for bigtop/slaves trunk images.
>>>>> Any thoughts?
>>>>
>>>> Check the java version, somehow the java docs whatever stuff
>>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>>>> Might be linked.
>>>>
>>>> Arnaud.
>>>>
>>>
>>>
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Explicitly adding Rvs in the loop
--
With regards,
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 Sat, Sep 23, 2017 at 12:24 PM, Evans Ye <ev...@apache.org> wrote:
> Hi Bigtoper,
>
> I'm working on the 1.2.1 release. Hopefully we can get it to the finish
> line by the end on Sept.
>
> Right now we still have a few issues blocking:
>
> 1. GPDB build failed on OpenSuSE 42.1[1]
> 2. Toolchain build failed on PPC64LE platform[2]
>
> I'll update more down the path. But right now I'd like to seek for some
> helps on GPDB and PPC64LE side ;)
>
>
> [1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> [2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>
>
> 2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
>
>> Thanks, Arnaud
>>
>> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
>> bigtop/slaves:1.2.1-$OS bash -l
>> root@596ef2c638de:/# java -version
>> openjdk version "1.8.0_131"
>> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
>> 16.04.2-b11)
>> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>>
>> Looks linked!
>>
>>
>> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>>
>>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>>> > 1. Somehow packages on centos and debian changed. If we rebuild
>>> > bigtop/slaves for trunk, then Solr will fail the same as what we faced
>>> > building with 1.2.1 images.
>>> > 2. We've special tweaks for bigtop/slaves trunk images.
>>> > Any thoughts?
>>>
>>> Check the java version, somehow the java docs whatever stuff
>>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>>> Might be linked.
>>>
>>> Arnaud.
>>>
>>
>>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Hi Bigtoper,
I'm working on the 1.2.1 release. Hopefully we can get it to the finish
line by the end on Sept.
Right now we still have a few issues blocking:
1. GPDB build failed on OpenSuSE 42.1[1]
2. Toolchain build failed on PPC64LE platform[2]
I'll update more down the path. But right now I'd like to seek for some
helps on GPDB and PPC64LE side ;)
[1]. https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
[2]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
2017-07-26 11:24 GMT+08:00 Evans Ye <ev...@apache.org>:
> Thanks, Arnaud
>
> [jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
> bigtop/slaves:1.2.1-$OS bash -l
> root@596ef2c638de:/# java -version
> openjdk version "1.8.0_131"
> OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.
> 16.04.2-b11)
> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
>
> Looks linked!
>
>
> 2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
>
>> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
>> > 1. Somehow packages on centos and debian changed. If we rebuild
>> > bigtop/slaves for trunk, then Solr will fail the same as what we faced
>> > building with 1.2.1 images.
>> > 2. We've special tweaks for bigtop/slaves trunk images.
>> > Any thoughts?
>>
>> Check the java version, somehow the java docs whatever stuff
>> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
>> Might be linked.
>>
>> Arnaud.
>>
>
>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Thanks, Arnaud
[jenkins@ip bigtop-ubuntu-16.04]$ docker run -ti --rm
bigtop/slaves:1.2.1-$OS bash -l
root@596ef2c638de:/# java -version
openjdk version "1.8.0_131"
OpenJDK Runtime Environment (build 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11)
OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
Looks linked!
2017-07-26 3:02 GMT+08:00 Arnaud Launay <as...@launay.org>:
> Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> > 1. Somehow packages on centos and debian changed. If we rebuild
> > bigtop/slaves for trunk, then Solr will fail the same as what we faced
> > building with 1.2.1 images.
> > 2. We've special tweaks for bigtop/slaves trunk images.
> > Any thoughts?
>
> Check the java version, somehow the java docs whatever stuff
> changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
> Might be linked.
>
> Arnaud.
>
Re: Releasing 1.2.1
Posted by Arnaud Launay <as...@launay.org>.
Le Wed, Jul 26, 2017 at 12:45:50AM +0800, Evans Ye a écrit:
> 1. Somehow packages on centos and debian changed. If we rebuild
> bigtop/slaves for trunk, then Solr will fail the same as what we faced
> building with 1.2.1 images.
> 2. We've special tweaks for bigtop/slaves trunk images.
> Any thoughts?
Check the java version, somehow the java docs whatever stuff
changed in 8.131, and solr doesn't compile anymore with java8 >=131 .
Might be linked.
Arnaud.
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Hi all,
I'm currently hitting a strange problem building 1.2.1 packages.
Solr fails to build on centos-6, centos-7, debian-8, and fedora-25[1].
But according to our CI for trunk packages[2], they should be OK except on
Fedora.
I've tried to use trunk images building Solr manually on centos and debian.
It works.
Since branch-1.2 has master merged in, the code should be no difference.
Therefore I can only imaging the following two possibilities:
1. Somehow packages on centos and debian changed. If we rebuild
bigtop/slaves for trunk, then Solr will fail the same as what we faced
building with 1.2.1 images.
2. We've special tweaks for bigtop/slaves trunk images.
Any thoughts?
Evans
[1]. https://ci.bigtop.apache.org/job/Bigtop-1.2.1/
[2]. https://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/
2017-07-22 2:37 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> Got it, that makes sense.
> I have added this note to
> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
>
> Thanks,
> Cos
> --
> With regards,
> 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 Fri, Jul 21, 2017 at 10:11 AM, Evans Ye <ev...@apache.org> wrote:
> > urgh...
> > This is a bit off document, but good to be brought up.
> > The fact is we got 3 * 1T donated storages. Hence 1T for master, and
> > another 2 * 1T goes to 06 and 07, respectively. Without storage we only
> got
> > 40G for each node to operate, which can't fit docker images in at all.
> > Therefore only 06 and 07 enabled to build packages.
> >
> > 02 and 03 are deployed to run non storage sensitive jobs such as
> > provisioner.
> >
> > 2017-07-22 0:18 GMT+08:00 Konstantin Boudnik <co...@boudnik.org>:
> >
> >> Only slightly off-topic: I am looking at the CI and see that only
> >> slaves 06 and 07 are used for x86 builds. Is there any reason we
> >> aren't utilizing 02 and 03? May be I am missing something, but adding
> >> those to the queue would cut our build times about 50%, no?
> >> --
> >> With regards,
> >> Konstantin (Cos) Boudnik
> >>
> >>
> >> On Wed, Jul 19, 2017 at 10:54 AM, Evans Ye <ev...@apache.org> wrote:
> >> > Hi Peter,
> >> >
> >> > What do you mean by: That said, *not* releasing on 42.1 is not an
> issue
> >> for
> >> > me. 42.3 is about
> >> > If that's a signal to bump Bigtop supported opensuse to 42.3, then we
> can
> >> > try.
> >> > But one thing we need your help is to get 42.3 official image on the
> >> shelf:
> >> > https://hub.docker.com/r/library/opensuse/tags/
> >> >
> >> > I've dig around for the current 42.1 slave image build and most likely
> >> it's
> >> > a package conflict issue.
> >> > If 42.3 image is not gonna happened soon. How about 42.2?
> >> >
> >> >
> >> >
> >> >
> >> > 2017-07-15 5:46 GMT+08:00 Peter Linnell <pl...@apache.org>:
> >> >
> >> >> On Thu, 13 Jul 2017 19:16:32 -0700
> >> >> Konstantin Boudnik <co...@apache.org> wrote:
> >> >>
> >> >> > Shall we bump the Suse version then?
> >> >>
> >> >>
> >> >> <snip>
> >> >>
> >> >> Yes. definitely.
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Peter
> >> >>
> >>
>
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Got it, that makes sense.
I have added this note to
https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
Thanks,
Cos
--
With regards,
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 Fri, Jul 21, 2017 at 10:11 AM, Evans Ye <ev...@apache.org> wrote:
> urgh...
> This is a bit off document, but good to be brought up.
> The fact is we got 3 * 1T donated storages. Hence 1T for master, and
> another 2 * 1T goes to 06 and 07, respectively. Without storage we only got
> 40G for each node to operate, which can't fit docker images in at all.
> Therefore only 06 and 07 enabled to build packages.
>
> 02 and 03 are deployed to run non storage sensitive jobs such as
> provisioner.
>
> 2017-07-22 0:18 GMT+08:00 Konstantin Boudnik <co...@boudnik.org>:
>
>> Only slightly off-topic: I am looking at the CI and see that only
>> slaves 06 and 07 are used for x86 builds. Is there any reason we
>> aren't utilizing 02 and 03? May be I am missing something, but adding
>> those to the queue would cut our build times about 50%, no?
>> --
>> With regards,
>> Konstantin (Cos) Boudnik
>>
>>
>> On Wed, Jul 19, 2017 at 10:54 AM, Evans Ye <ev...@apache.org> wrote:
>> > Hi Peter,
>> >
>> > What do you mean by: That said, *not* releasing on 42.1 is not an issue
>> for
>> > me. 42.3 is about
>> > If that's a signal to bump Bigtop supported opensuse to 42.3, then we can
>> > try.
>> > But one thing we need your help is to get 42.3 official image on the
>> shelf:
>> > https://hub.docker.com/r/library/opensuse/tags/
>> >
>> > I've dig around for the current 42.1 slave image build and most likely
>> it's
>> > a package conflict issue.
>> > If 42.3 image is not gonna happened soon. How about 42.2?
>> >
>> >
>> >
>> >
>> > 2017-07-15 5:46 GMT+08:00 Peter Linnell <pl...@apache.org>:
>> >
>> >> On Thu, 13 Jul 2017 19:16:32 -0700
>> >> Konstantin Boudnik <co...@apache.org> wrote:
>> >>
>> >> > Shall we bump the Suse version then?
>> >>
>> >>
>> >> <snip>
>> >>
>> >> Yes. definitely.
>> >>
>> >> Thanks,
>> >>
>> >> Peter
>> >>
>>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
urgh...
This is a bit off document, but good to be brought up.
The fact is we got 3 * 1T donated storages. Hence 1T for master, and
another 2 * 1T goes to 06 and 07, respectively. Without storage we only got
40G for each node to operate, which can't fit docker images in at all.
Therefore only 06 and 07 enabled to build packages.
02 and 03 are deployed to run non storage sensitive jobs such as
provisioner.
2017-07-22 0:18 GMT+08:00 Konstantin Boudnik <co...@boudnik.org>:
> Only slightly off-topic: I am looking at the CI and see that only
> slaves 06 and 07 are used for x86 builds. Is there any reason we
> aren't utilizing 02 and 03? May be I am missing something, but adding
> those to the queue would cut our build times about 50%, no?
> --
> With regards,
> Konstantin (Cos) Boudnik
>
>
> On Wed, Jul 19, 2017 at 10:54 AM, Evans Ye <ev...@apache.org> wrote:
> > Hi Peter,
> >
> > What do you mean by: That said, *not* releasing on 42.1 is not an issue
> for
> > me. 42.3 is about
> > If that's a signal to bump Bigtop supported opensuse to 42.3, then we can
> > try.
> > But one thing we need your help is to get 42.3 official image on the
> shelf:
> > https://hub.docker.com/r/library/opensuse/tags/
> >
> > I've dig around for the current 42.1 slave image build and most likely
> it's
> > a package conflict issue.
> > If 42.3 image is not gonna happened soon. How about 42.2?
> >
> >
> >
> >
> > 2017-07-15 5:46 GMT+08:00 Peter Linnell <pl...@apache.org>:
> >
> >> On Thu, 13 Jul 2017 19:16:32 -0700
> >> Konstantin Boudnik <co...@apache.org> wrote:
> >>
> >> > Shall we bump the Suse version then?
> >>
> >>
> >> <snip>
> >>
> >> Yes. definitely.
> >>
> >> Thanks,
> >>
> >> Peter
> >>
>
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@boudnik.org>.
Only slightly off-topic: I am looking at the CI and see that only
slaves 06 and 07 are used for x86 builds. Is there any reason we
aren't utilizing 02 and 03? May be I am missing something, but adding
those to the queue would cut our build times about 50%, no?
--
With regards,
Konstantin (Cos) Boudnik
On Wed, Jul 19, 2017 at 10:54 AM, Evans Ye <ev...@apache.org> wrote:
> Hi Peter,
>
> What do you mean by: That said, *not* releasing on 42.1 is not an issue for
> me. 42.3 is about
> If that's a signal to bump Bigtop supported opensuse to 42.3, then we can
> try.
> But one thing we need your help is to get 42.3 official image on the shelf:
> https://hub.docker.com/r/library/opensuse/tags/
>
> I've dig around for the current 42.1 slave image build and most likely it's
> a package conflict issue.
> If 42.3 image is not gonna happened soon. How about 42.2?
>
>
>
>
> 2017-07-15 5:46 GMT+08:00 Peter Linnell <pl...@apache.org>:
>
>> On Thu, 13 Jul 2017 19:16:32 -0700
>> Konstantin Boudnik <co...@apache.org> wrote:
>>
>> > Shall we bump the Suse version then?
>>
>>
>> <snip>
>>
>> Yes. definitely.
>>
>> Thanks,
>>
>> Peter
>>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Hi Peter,
What do you mean by: That said, *not* releasing on 42.1 is not an issue for
me. 42.3 is about
If that's a signal to bump Bigtop supported opensuse to 42.3, then we can
try.
But one thing we need your help is to get 42.3 official image on the shelf:
https://hub.docker.com/r/library/opensuse/tags/
I've dig around for the current 42.1 slave image build and most likely it's
a package conflict issue.
If 42.3 image is not gonna happened soon. How about 42.2?
2017-07-15 5:46 GMT+08:00 Peter Linnell <pl...@apache.org>:
> On Thu, 13 Jul 2017 19:16:32 -0700
> Konstantin Boudnik <co...@apache.org> wrote:
>
> > Shall we bump the Suse version then?
>
>
> <snip>
>
> Yes. definitely.
>
> Thanks,
>
> Peter
>
Re: Releasing 1.2.1
Posted by Peter Linnell <pl...@apache.org>.
On Thu, 13 Jul 2017 19:16:32 -0700
Konstantin Boudnik <co...@apache.org> wrote:
> Shall we bump the Suse version then?
<snip>
Yes. definitely.
Thanks,
Peter
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Shall we bump the Suse version then?
--
With regards,
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, Jul 13, 2017 at 6:58 PM, Peter Linnell <pl...@apache.org> wrote:
> Hi all,
>
> Sorry for the late reply.
>
> I'll look into this tonight.
>
> That said, *not* releasing on 42.1 is not an issue for me. 42.3 is about
> to be out in a few days.
>
> 42.3 has I believe much newer docker stuff it inheriting from SLE 12
> SP3.
>
> More later.
>
> Thanks,
> Peter
>
>
> On Wed, 12 Jul 2017 23:49:58 -0700
> Konstantin Boudnik <co...@apache.org> wrote:
>
>> Cc'ing Peter Linnell who might be able to help with Suse's issue...
>>
>> Cos
>> --
>> With regards,
>> 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 Wed, Jul 12, 2017 at 11:02 PM, Evans Ye <ev...@apache.org> wrote:
>> > Hi all,
>> >
>> > First of all, sorry for the delay of 1.2.1 release.
>> > The current status of release is blocked by building the docker
>> > slave image for SuSE 42.1[1].
>> >
>> > To reveal the whole picture, the pipeline to release will be looked
>> > like this on top of my head, :
>> >
>> > Build 1.2.1 Docker slave images --> Build 1.2.1 RPM/DEB packages
>> > --> Sign packages -> Upload artifacts to S3 -> Run through
>> > deployment test -> Vote for RC -> release
>> >
>> > I'm currently under a heavy pressure on my paid work, so the
>> > release has been pushed back on my todo list.
>> > If some one can help on removing the obstacles, it will be very much
>> > appreciated.
>> > I might be able to resume the release process in next week.
>> >
>> > Evans
>> >
>> > [1].
>> > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>> >
>> > 2017-07-06 12:35 GMT+08:00 Evans Ye <ev...@apache.org>:
>> >
>> >> Sure.
>> >> The master is not freezing. Ive merge things back in branch 1.2.
>> >>
>> >> Konstantin Boudnik <co...@apache.org>於 2017年7月6日
>> >> 週四，上午3:55寫道：
>> >>> BTW, Evans - I assume it is ok to re-start committing into the
>> >>> master as you
>> >>> have merged master back to branch-1.2 already, right?
>> >>>
>> >>> Thanks,
>> >>> Cos
>> >>>
>> >>> On Wed, Jul 05, 2017 at 11:14AM, Konstantin Boudnik wrote:
>> >>> > Thanks for pushing this through, Evans!
>> >>> >
>> >>> > As for the iTest's failures on 16.04: we need to revisit the
>> >>> > test suite, considering that some of these could have bit-rot
>> >>> > since they were
>> >>> written.
>> >>> > Last recollection I have is about releasing 1.0 or 1.1 and
>> >>> > running
>> >>> those on
>> >>> > the supported Ubuntu (which seemed to be ok at the time).
>> >>> >
>> >>> > I would look into the init.d specific tests as a part of 1.3.
>> >>> Especially,
>> >>> > considering that the same failures are observed in 1.2 and no
>> >>> regressions are
>> >>> > introduced. Does it make sense?
>> >>> >
>> >>> > Cos
>> >>> >
>> >>> > On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
>> >>> > > I got even more errors when running on CentOS 6...
>> >>> > > Finally I was able to pass all the test cases if running on
>> >>> > > Ubuntu
>> >>> 14.04
>> >>> > > with BIGTOP-2829
>> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> patched.
>> >>> > > Ubuntu-16.04 is not working: BIGTOP-2830
>> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2830>.
>> >>> > >
>> >>> > > The RC1 is ready just for walking through the process:
>> >>> > > https://dist.apache.org/repos/dist/dev/bigtop/
>> >>> > > I need to add BIGTOP-2829
>> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> and
>> >>> > > BIGTOP-2819
>> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there
>> >>> > > will
>> >>> be a RC2
>> >>> > > soon.
>> >>> > >
>> >>> > > There are some works on my todo list before the release:
>> >>> > > 1. Publish 1.2.1 build slaves
>> >>> > > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>> >>> > > 2. Upload 1.2.1 binary artifacts
>> >>> > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>> >>> > >
>> >>> > > Regarding to release, all the issues I've encountered has
>> >>> > > been
>> >>> updated on
>> >>> > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
>> >>> > >
>> >>> > > Since I'm not familiar with iTest, can some one chime in for
>> >>> > > a double confirm for the patch and the process? Thanks!
>> >>> > >
>> >>> > > Evans
>> >>> > >
>> >>> > >
>> >>> > >
>> >>> > > 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>> >>> > >
>> >>> > > > Hi Evans,
>> >>> > > >
>> >>> > > > I never used the iTests. However looking at the code, it
>> >>> > > > can not
>> >>> work on
>> >>> > > > ubuntu-16.04 since the code is assuming a init system,
>> >>> > > > rather
>> >>> systemd.
>> >>> > > >
>> >>> > > > You may try centos-6
>> >>> > > >
>> >>> > > >
>> >>> > > > Running org.apache.bigtop.itest.posix.ServiceTest
>> >>> > > >
>> >>> > > >
>> >>> > > > Olaf
>> >>> > > >
>> >>>
>> >>
>
Re: Releasing 1.2.1
Posted by Peter Linnell <pl...@apache.org>.
Hi all,
Sorry for the late reply.
I'll look into this tonight.
That said, *not* releasing on 42.1 is not an issue for me. 42.3 is about
to be out in a few days.
42.3 has I believe much newer docker stuff it inheriting from SLE 12
SP3.
More later.
Thanks,
Peter
On Wed, 12 Jul 2017 23:49:58 -0700
Konstantin Boudnik <co...@apache.org> wrote:
> Cc'ing Peter Linnell who might be able to help with Suse's issue...
>
> Cos
> --
> With regards,
> 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 Wed, Jul 12, 2017 at 11:02 PM, Evans Ye <ev...@apache.org> wrote:
> > Hi all,
> >
> > First of all, sorry for the delay of 1.2.1 release.
> > The current status of release is blocked by building the docker
> > slave image for SuSE 42.1[1].
> >
> > To reveal the whole picture, the pipeline to release will be looked
> > like this on top of my head, :
> >
> > Build 1.2.1 Docker slave images --> Build 1.2.1 RPM/DEB packages
> > --> Sign packages -> Upload artifacts to S3 -> Run through
> > deployment test -> Vote for RC -> release
> >
> > I'm currently under a heavy pressure on my paid work, so the
> > release has been pushed back on my todo list.
> > If some one can help on removing the obstacles, it will be very much
> > appreciated.
> > I might be able to resume the release process in next week.
> >
> > Evans
> >
> > [1].
> > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
> >
> > 2017-07-06 12:35 GMT+08:00 Evans Ye <ev...@apache.org>:
> >
> >> Sure.
> >> The master is not freezing. Ive merge things back in branch 1.2.
> >>
> >> Konstantin Boudnik <co...@apache.org>於 2017年7月6日
> >> 週四，上午3:55寫道：
> >>> BTW, Evans - I assume it is ok to re-start committing into the
> >>> master as you
> >>> have merged master back to branch-1.2 already, right?
> >>>
> >>> Thanks,
> >>> Cos
> >>>
> >>> On Wed, Jul 05, 2017 at 11:14AM, Konstantin Boudnik wrote:
> >>> > Thanks for pushing this through, Evans!
> >>> >
> >>> > As for the iTest's failures on 16.04: we need to revisit the
> >>> > test suite, considering that some of these could have bit-rot
> >>> > since they were
> >>> written.
> >>> > Last recollection I have is about releasing 1.0 or 1.1 and
> >>> > running
> >>> those on
> >>> > the supported Ubuntu (which seemed to be ok at the time).
> >>> >
> >>> > I would look into the init.d specific tests as a part of 1.3.
> >>> Especially,
> >>> > considering that the same failures are observed in 1.2 and no
> >>> regressions are
> >>> > introduced. Does it make sense?
> >>> >
> >>> > Cos
> >>> >
> >>> > On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
> >>> > > I got even more errors when running on CentOS 6...
> >>> > > Finally I was able to pass all the test cases if running on
> >>> > > Ubuntu
> >>> 14.04
> >>> > > with BIGTOP-2829
> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> patched.
> >>> > > Ubuntu-16.04 is not working: BIGTOP-2830
> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2830>.
> >>> > >
> >>> > > The RC1 is ready just for walking through the process:
> >>> > > https://dist.apache.org/repos/dist/dev/bigtop/
> >>> > > I need to add BIGTOP-2829
> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> and
> >>> > > BIGTOP-2819
> >>> > > <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there
> >>> > > will
> >>> be a RC2
> >>> > > soon.
> >>> > >
> >>> > > There are some works on my todo list before the release:
> >>> > > 1. Publish 1.2.1 build slaves
> >>> > > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
> >>> > > 2. Upload 1.2.1 binary artifacts
> >>> > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> >>> > >
> >>> > > Regarding to release, all the issues I've encountered has
> >>> > > been
> >>> updated on
> >>> > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
> >>> > >
> >>> > > Since I'm not familiar with iTest, can some one chime in for
> >>> > > a double confirm for the patch and the process? Thanks!
> >>> > >
> >>> > > Evans
> >>> > >
> >>> > >
> >>> > >
> >>> > > 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> >>> > >
> >>> > > > Hi Evans,
> >>> > > >
> >>> > > > I never used the iTests. However looking at the code, it
> >>> > > > can not
> >>> work on
> >>> > > > ubuntu-16.04 since the code is assuming a init system,
> >>> > > > rather
> >>> systemd.
> >>> > > >
> >>> > > > You may try centos-6
> >>> > > >
> >>> > > >
> >>> > > > Running org.apache.bigtop.itest.posix.ServiceTest
> >>> > > >
> >>> > > >
> >>> > > > Olaf
> >>> > > >
> >>>
> >>
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Cc'ing Peter Linnell who might be able to help with Suse's issue...
Cos
--
With regards,
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 Wed, Jul 12, 2017 at 11:02 PM, Evans Ye <ev...@apache.org> wrote:
> Hi all,
>
> First of all, sorry for the delay of 1.2.1 release.
> The current status of release is blocked by building the docker slave image
> for SuSE 42.1[1].
>
> To reveal the whole picture, the pipeline to release will be looked like
> this on top of my head, :
>
> Build 1.2.1 Docker slave images --> Build 1.2.1 RPM/DEB packages --> Sign
> packages -> Upload artifacts to S3 -> Run through deployment test -> Vote
> for RC -> release
>
> I'm currently under a heavy pressure on my paid work, so the release has
> been pushed back on my todo list.
> If some one can help on removing the obstacles, it will be very much
> appreciated.
> I might be able to resume the release process in next week.
>
> Evans
>
> [1]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>
> 2017-07-06 12:35 GMT+08:00 Evans Ye <ev...@apache.org>:
>
>> Sure.
>> The master is not freezing. Ive merge things back in branch 1.2.
>>
>> Konstantin Boudnik <co...@apache.org>於 2017年7月6日 週四，上午3:55寫道：
>>
>>> BTW, Evans - I assume it is ok to re-start committing into the master as
>>> you
>>> have merged master back to branch-1.2 already, right?
>>>
>>> Thanks,
>>> Cos
>>>
>>> On Wed, Jul 05, 2017 at 11:14AM, Konstantin Boudnik wrote:
>>> > Thanks for pushing this through, Evans!
>>> >
>>> > As for the iTest's failures on 16.04: we need to revisit the test suite,
>>> > considering that some of these could have bit-rot since they were
>>> written.
>>> > Last recollection I have is about releasing 1.0 or 1.1 and running
>>> those on
>>> > the supported Ubuntu (which seemed to be ok at the time).
>>> >
>>> > I would look into the init.d specific tests as a part of 1.3.
>>> Especially,
>>> > considering that the same failures are observed in 1.2 and no
>>> regressions are
>>> > introduced. Does it make sense?
>>> >
>>> > Cos
>>> >
>>> > On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
>>> > > I got even more errors when running on CentOS 6...
>>> > > Finally I was able to pass all the test cases if running on Ubuntu
>>> 14.04
>>> > > with BIGTOP-2829 <https://issues.apache.org/jira/browse/BIGTOP-2829>
>>> > > patched.
>>> > > Ubuntu-16.04 is not working: BIGTOP-2830
>>> > > <https://issues.apache.org/jira/browse/BIGTOP-2830>.
>>> > >
>>> > > The RC1 is ready just for walking through the process:
>>> > > https://dist.apache.org/repos/dist/dev/bigtop/
>>> > > I need to add BIGTOP-2829
>>> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> and BIGTOP-2819
>>> > > <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there will
>>> be a RC2
>>> > > soon.
>>> > >
>>> > > There are some works on my todo list before the release:
>>> > > 1. Publish 1.2.1 build slaves
>>> > > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>>> > > 2. Upload 1.2.1 binary artifacts
>>> > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>>> > >
>>> > > Regarding to release, all the issues I've encountered has been
>>> updated on
>>> > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
>>> > >
>>> > > Since I'm not familiar with iTest, can some one chime in for a double
>>> > > confirm for the patch and the process? Thanks!
>>> > >
>>> > > Evans
>>> > >
>>> > >
>>> > >
>>> > > 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>>> > >
>>> > > > Hi Evans,
>>> > > >
>>> > > > I never used the iTests. However looking at the code, it can not
>>> work on
>>> > > > ubuntu-16.04 since the code is assuming a init system, rather
>>> systemd.
>>> > > >
>>> > > > You may try centos-6
>>> > > >
>>> > > >
>>> > > > Running org.apache.bigtop.itest.posix.ServiceTest
>>> > > >
>>> > > >
>>> > > > Olaf
>>> > > >
>>>
>>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Hi all,
First of all, sorry for the delay of 1.2.1 release.
The current status of release is blocked by building the docker slave image
for SuSE 42.1[1].
To reveal the whole picture, the pipeline to release will be looked like
this on top of my head, :
Build 1.2.1 Docker slave images --> Build 1.2.1 RPM/DEB packages --> Sign
packages -> Upload artifacts to S3 -> Run through deployment test -> Vote
for RC -> release
I'm currently under a heavy pressure on my paid work, so the release has
been pushed back on my todo list.
If some one can help on removing the obstacles, it will be very much
appreciated.
I might be able to resume the release process in next week.
Evans
[1]. https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
2017-07-06 12:35 GMT+08:00 Evans Ye <ev...@apache.org>:
> Sure.
> The master is not freezing. Ive merge things back in branch 1.2.
>
> Konstantin Boudnik <co...@apache.org>於 2017年7月6日 週四，上午3:55寫道：
>
>> BTW, Evans - I assume it is ok to re-start committing into the master as
>> you
>> have merged master back to branch-1.2 already, right?
>>
>> Thanks,
>> Cos
>>
>> On Wed, Jul 05, 2017 at 11:14AM, Konstantin Boudnik wrote:
>> > Thanks for pushing this through, Evans!
>> >
>> > As for the iTest's failures on 16.04: we need to revisit the test suite,
>> > considering that some of these could have bit-rot since they were
>> written.
>> > Last recollection I have is about releasing 1.0 or 1.1 and running
>> those on
>> > the supported Ubuntu (which seemed to be ok at the time).
>> >
>> > I would look into the init.d specific tests as a part of 1.3.
>> Especially,
>> > considering that the same failures are observed in 1.2 and no
>> regressions are
>> > introduced. Does it make sense?
>> >
>> > Cos
>> >
>> > On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
>> > > I got even more errors when running on CentOS 6...
>> > > Finally I was able to pass all the test cases if running on Ubuntu
>> 14.04
>> > > with BIGTOP-2829 <https://issues.apache.org/jira/browse/BIGTOP-2829>
>> > > patched.
>> > > Ubuntu-16.04 is not working: BIGTOP-2830
>> > > <https://issues.apache.org/jira/browse/BIGTOP-2830>.
>> > >
>> > > The RC1 is ready just for walking through the process:
>> > > https://dist.apache.org/repos/dist/dev/bigtop/
>> > > I need to add BIGTOP-2829
>> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> and BIGTOP-2819
>> > > <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there will
>> be a RC2
>> > > soon.
>> > >
>> > > There are some works on my todo list before the release:
>> > > 1. Publish 1.2.1 build slaves
>> > > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
>> > > 2. Upload 1.2.1 binary artifacts
>> > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>> > >
>> > > Regarding to release, all the issues I've encountered has been
>> updated on
>> > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
>> > >
>> > > Since I'm not familiar with iTest, can some one chime in for a double
>> > > confirm for the patch and the process? Thanks!
>> > >
>> > > Evans
>> > >
>> > >
>> > >
>> > > 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>> > >
>> > > > Hi Evans,
>> > > >
>> > > > I never used the iTests. However looking at the code, it can not
>> work on
>> > > > ubuntu-16.04 since the code is assuming a init system, rather
>> systemd.
>> > > >
>> > > > You may try centos-6
>> > > >
>> > > >
>> > > > Running org.apache.bigtop.itest.posix.ServiceTest
>> > > >
>> > > >
>> > > > Olaf
>> > > >
>>
>
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
Sure.
The master is not freezing. Ive merge things back in branch 1.2.
Konstantin Boudnik <co...@apache.org>於 2017年7月6日 週四，上午3:55寫道：
> BTW, Evans - I assume it is ok to re-start committing into the master as
> you
> have merged master back to branch-1.2 already, right?
>
> Thanks,
> Cos
>
> On Wed, Jul 05, 2017 at 11:14AM, Konstantin Boudnik wrote:
> > Thanks for pushing this through, Evans!
> >
> > As for the iTest's failures on 16.04: we need to revisit the test suite,
> > considering that some of these could have bit-rot since they were
> written.
> > Last recollection I have is about releasing 1.0 or 1.1 and running those
> on
> > the supported Ubuntu (which seemed to be ok at the time).
> >
> > I would look into the init.d specific tests as a part of 1.3. Especially,
> > considering that the same failures are observed in 1.2 and no
> regressions are
> > introduced. Does it make sense?
> >
> > Cos
> >
> > On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
> > > I got even more errors when running on CentOS 6...
> > > Finally I was able to pass all the test cases if running on Ubuntu
> 14.04
> > > with BIGTOP-2829 <https://issues.apache.org/jira/browse/BIGTOP-2829>
> > > patched.
> > > Ubuntu-16.04 is not working: BIGTOP-2830
> > > <https://issues.apache.org/jira/browse/BIGTOP-2830>.
> > >
> > > The RC1 is ready just for walking through the process:
> > > https://dist.apache.org/repos/dist/dev/bigtop/
> > > I need to add BIGTOP-2829
> > > <https://issues.apache.org/jira/browse/BIGTOP-2829> and BIGTOP-2819
> > > <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there will be
> a RC2
> > > soon.
> > >
> > > There are some works on my todo list before the release:
> > > 1. Publish 1.2.1 build slaves
> > > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
> > > 2. Upload 1.2.1 binary artifacts
> > > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> > >
> > > Regarding to release, all the issues I've encountered has been updated
> on
> > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
> > >
> > > Since I'm not familiar with iTest, can some one chime in for a double
> > > confirm for the patch and the process? Thanks!
> > >
> > > Evans
> > >
> > >
> > >
> > > 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> > >
> > > > Hi Evans,
> > > >
> > > > I never used the iTests. However looking at the code, it can not
> work on
> > > > ubuntu-16.04 since the code is assuming a init system, rather
> systemd.
> > > >
> > > > You may try centos-6
> > > >
> > > >
> > > > Running org.apache.bigtop.itest.posix.ServiceTest
> > > >
> > > >
> > > > Olaf
> > > >
>
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
BTW, Evans - I assume it is ok to re-start committing into the master as you
have merged master back to branch-1.2 already, right?
Thanks,
Cos
On Wed, Jul 05, 2017 at 11:14AM, Konstantin Boudnik wrote:
> Thanks for pushing this through, Evans!
>
> As for the iTest's failures on 16.04: we need to revisit the test suite,
> considering that some of these could have bit-rot since they were written.
> Last recollection I have is about releasing 1.0 or 1.1 and running those on
> the supported Ubuntu (which seemed to be ok at the time).
>
> I would look into the init.d specific tests as a part of 1.3. Especially,
> considering that the same failures are observed in 1.2 and no regressions are
> introduced. Does it make sense?
>
> Cos
>
> On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
> > I got even more errors when running on CentOS 6...
> > Finally I was able to pass all the test cases if running on Ubuntu 14.04
> > with BIGTOP-2829 <https://issues.apache.org/jira/browse/BIGTOP-2829>
> > patched.
> > Ubuntu-16.04 is not working: BIGTOP-2830
> > <https://issues.apache.org/jira/browse/BIGTOP-2830>.
> >
> > The RC1 is ready just for walking through the process:
> > https://dist.apache.org/repos/dist/dev/bigtop/
> > I need to add BIGTOP-2829
> > <https://issues.apache.org/jira/browse/BIGTOP-2829> and BIGTOP-2819
> > <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there will be a RC2
> > soon.
> >
> > There are some works on my todo list before the release:
> > 1. Publish 1.2.1 build slaves
> > https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
> > 2. Upload 1.2.1 binary artifacts
> > https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
> >
> > Regarding to release, all the issues I've encountered has been updated on
> > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
> >
> > Since I'm not familiar with iTest, can some one chime in for a double
> > confirm for the patch and the process? Thanks!
> >
> > Evans
> >
> >
> >
> > 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> >
> > > Hi Evans,
> > >
> > > I never used the iTests. However looking at the code, it can not work on
> > > ubuntu-16.04 since the code is assuming a init system, rather systemd.
> > >
> > > You may try centos-6
> > >
> > >
> > > Running org.apache.bigtop.itest.posix.ServiceTest
> > >
> > >
> > > Olaf
> > >
Re: Releasing 1.2.1
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks for pushing this through, Evans!
As for the iTest's failures on 16.04: we need to revisit the test suite,
considering that some of these could have bit-rot since they were written.
Last recollection I have is about releasing 1.0 or 1.1 and running those on
the supported Ubuntu (which seemed to be ok at the time).
I would look into the init.d specific tests as a part of 1.3. Especially,
considering that the same failures are observed in 1.2 and no regressions are
introduced. Does it make sense?
Cos
On Mon, Jul 03, 2017 at 01:59AM, Evans Ye wrote:
> I got even more errors when running on CentOS 6...
> Finally I was able to pass all the test cases if running on Ubuntu 14.04
> with BIGTOP-2829 <https://issues.apache.org/jira/browse/BIGTOP-2829>
> patched.
> Ubuntu-16.04 is not working: BIGTOP-2830
> <https://issues.apache.org/jira/browse/BIGTOP-2830>.
>
> The RC1 is ready just for walking through the process:
> https://dist.apache.org/repos/dist/dev/bigtop/
> I need to add BIGTOP-2829
> <https://issues.apache.org/jira/browse/BIGTOP-2829> and BIGTOP-2819
> <https://issues.apache.org/jira/browse/BIGTOP-2819>. So there will be a RC2
> soon.
>
> There are some works on my todo list before the release:
> 1. Publish 1.2.1 build slaves
> https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
> 2. Upload 1.2.1 binary artifacts
> https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
>
> Regarding to release, all the issues I've encountered has been updated on
> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
>
> Since I'm not familiar with iTest, can some one chime in for a double
> confirm for the patch and the process? Thanks!
>
> Evans
>
>
>
> 2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
>
> > Hi Evans,
> >
> > I never used the iTests. However looking at the code, it can not work on
> > ubuntu-16.04 since the code is assuming a init system, rather systemd.
> >
> > You may try centos-6
> >
> >
> > Running org.apache.bigtop.itest.posix.ServiceTest
> >
> >
> > Olaf
> >
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
I got even more errors when running on CentOS 6...
Finally I was able to pass all the test cases if running on Ubuntu 14.04
with BIGTOP-2829 <https://issues.apache.org/jira/browse/BIGTOP-2829>
patched.
Ubuntu-16.04 is not working: BIGTOP-2830
<https://issues.apache.org/jira/browse/BIGTOP-2830>.
The RC1 is ready just for walking through the process:
https://dist.apache.org/repos/dist/dev/bigtop/
I need to add BIGTOP-2829
<https://issues.apache.org/jira/browse/BIGTOP-2829> and BIGTOP-2819
<https://issues.apache.org/jira/browse/BIGTOP-2819>. So there will be a RC2
soon.
There are some works on my todo list before the release:
1. Publish 1.2.1 build slaves
https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.2.1/
2. Upload 1.2.1 binary artifacts
https://ci.bigtop.apache.org/view/Releases/job/Bigtop-1.2.1/
Regarding to release, all the issues I've encountered has been updated on
https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
Since I'm not familiar with iTest, can some one chime in for a double
confirm for the patch and the process? Thanks!
Evans
2017-07-02 2:24 GMT+08:00 Olaf Flebbe <of...@oflebbe.de>:
> Hi Evans,
>
> I never used the iTests. However looking at the code, it can not work on
> ubuntu-16.04 since the code is assuming a init system, rather systemd.
>
> You may try centos-6
>
>
> Running org.apache.bigtop.itest.posix.ServiceTest
>
>
> Olaf
>
Re: Releasing 1.2.1
Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi Evans,
I never used the iTests. However looking at the code, it can not work on ubuntu-16.04 since the code is assuming a init system, rather systemd.
You may try centos-6
>
> Running org.apache.bigtop.itest.posix.ServiceTest
Olaf
Re: Releasing 1.2.1
Posted by Evans Ye <ev...@apache.org>.
BTW, I tried to run same commands against 1.2.0 code and it behaves the
same. ;)
2017-07-02 1:31 GMT+08:00 Evans Ye <ev...@apache.org>:
> Hi folks,
>
> As you may see I'm working on the 1.2.1 release right now.
>
> Basically what I did is to merge the master branch into branch-1.2 and
> have branch-1.2 and release-1.2.1-RC0 tag pushed.
> Then, I follow the release guide[1] to walk down the path.
> However, I'm currently stuck at:
>
> mvn deploy -Prelease -f bigtop-test-framework/pom.xml
>
> ...
> Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.153
> sec
> Running org.apache.bigtop.itest.posix.AlternativeTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.411 sec
> <<< FAILURE!
> Running org.apache.bigtop.itest.posix.ServiceTest
> Status []
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.04 sec
> Running org.apache.bigtop.itest.posix.UGITest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec
> Running org.apache.bigtop.itest.shell.ShellTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
> <<< FAILURE!
> Running org.apache.bigtop.itest.TestContractGroovy
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec
> Running org.apache.bigtop.itest.TestContractJava
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
> Running org.apache.bigtop.itest.TestContractJavaProc
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
> Running org.apache.bigtop.itest.TestListUtilsTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec
>
> Results :
>
> Failed tests:
> testGetAllAlternatives(org.apache.bigtop.itest.posix.AlternativeTest)
> regularUserShell(org.apache.bigtop.itest.shell.ShellTest)
>
> Tests run: 45, Failures: 2, Errors: 0, Skipped: 1
>
>
>
> I wonder is it an env issue? I've tried to build on ubuntu-16.04,
> debian-8, and centos-7.
> ubuntu-16.04 and debian-8 are the same(2 failures), but I got even more
> failed tests on centos-7.
>
> To attach more info, here's how I prepare my env:
>
> $ docker run -ti --rm -v $PWD:/tmp bigtop/slaves:trunk-ubuntu-16.04 bash
> -l
> $ cp -r /tmp/.gnupg ~/
> $ cd $(BIGTOP_REPO)
> $ mvn deploy -Prelease -f bigtop-test-framework/pom.xml
>
>
> I guess Cos and Roman who has done the release can give me more hints?
>
> Evans
>
>
> [1]. https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release
>
>