Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

AFAIK, the build slave for arm is offline in our CI: 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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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:

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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 : > > Well, if we can't fix it - let's nuke

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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:

Re: Releasing 1.2.1

Let me take a look today On Sat, Sep 23, 2017 at 9:34 AM, Konstantin Boudnik 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

Re: Releasing 1.2.1

Problem was the global jenkins setting 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

Re: Releasing 1.2.1

I think I can fix [2] Olaf > Am 23.09.2017 um 18:34 schrieb Konstantin Boudnik : > > 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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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)

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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)

Re: Releasing 1.2.1

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:

Re: Releasing 1.2.1

On Thu, 13 Jul 2017 19:16:32 -0700 Konstantin Boudnik wrote: > Shall we bump the Suse version then? Yes. definitely. Thanks, Peter

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

Sure. The master is not freezing. Ive merge things back in branch 1.2. Konstantin Boudnik 於 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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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

Re: Releasing 1.2.1

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 patched. Ubuntu-16.04 is not working: BIGTOP-2830 .

Re: Releasing 1.2.1

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 signature.asc Description: Message signed with OpenPGP

Re: Releasing 1.2.1

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 : > 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

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