Hi Marcin, we are in the same timezone :-) You may try to contact me on IRC. But not tonight any more, will leave shortly.
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 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. IMHO the hue patch will turn the hue red line to blue. 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. > > 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 > - bigtop-tomcat (have to check) ok? Will propose to update to 6.0.52 > - datafu (no gradle binary) ??? > - hbase (something about org.asciidoctor) It is fixed with 1.3. We had old versions in nexus. > - kafka (no gradle binary) ?? > - spark (no JAVA_HOME) ?? > - 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. > Sorry for short mail without many details but it is 22:00 here and I do > that only because Olaf is online and updates Jira so my MiBand 2 thing > interrupted watching some TV series ;D > Olaf
