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

Reply via email to