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