W dniu 04.12.2017 o 22:14, Olaf Flebbe pisze: > I like your approach first to reproduce. But I do not think it does > make sense to reproduce 1.2.1, lets advance on 1.3
I was asked for 1.2.1 too. > First things first. Do you know: > > https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/ ? > > Please create an account at the ci and I will look into it giving you > more rights that you can see the magic behind it. Its poorly > documented. Created "hrw" account there. > IMHO the hue patch will turn the hue red line to blue. Cool. > I will commit your oozie patch. I think it will not help and let > oozie fail differently. Hope you are able to reproduce that as well. oozie is blue again. >> Failures: >> >> - ambari (uses x86-64 nodejs binaries) > > noteable it is phantomjs. You may use the workaround from tez in > 1.2.1 (which I removed for 1.3) to solve ths issue. >> - bigtop-jsvc ("Java Home not defined") > I will propose to remove that because it is supplied by every linux > distro. Was there because of centos-6 built >> - bigtop-tomcat (have to check) > ok? Will propose to update to 6.0.52 built >> - datafu (no gradle binary) > ??? built >> - hbase (something about org.asciidoctor) > It is fixed with 1.3. We had old versions in nexus. > >> - kafka (no gradle binary) > ?? built >> - spark (no JAVA_HOME) > ?? built >> - tez (x86-64 nodejs binaries) > Solved in 1.3 >> Will take a look at failures. Also plan to do Bigtop 'master' build >> on fresh Debian 9 'stretch' aarch64 system to catch some bugs and >> to check existing fixes. > Do you have a stable docker for aarch64 ? This is a prerequiste for > advancing with bigtop. On Debian 'stretch' we have docker-ce 17.06 available. And 1.12.x for CentOS 7/Debian 8. I already used Docker during tests on x86-64. Plan to use dockerized way on aarch64 as well.
