I've tried here: http://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages-manual-component-test/ (ignore the opensuse, that's obviously an env issue)
It looks great. Ii only took 11~12 mins to build. Let me add it back in nightly build. Thanks Roman. 2016-01-11 14:44 GMT+08:00 Konstantin Boudnik <[email protected]>: > On Sun, Jan 10, 2016 at 08:44PM, Roman Shaposhnik wrote: > > On Sat, Jan 9, 2016 at 6:08 AM, Olaf Flebbe <[email protected]> wrote: > > > Hi Roman, > > > > > > I do not know if the german phrase translates correctly into english. > "I am getting an neck like this ..." ;-) > > > > ;-) > > > > > This package is a tremendous waste of resources in our CI. It needs > 1,5 hours compilation time of our > > > total 5 hour compilation. We will save over 15 elapsed hours (do not > know how it translates into > > > CPU hours) every day. (6 Bigtop-trunk-packages and 5 Bigtop-trunk). Of > course we are spending this in parallel ... > > > > > > There is an obvious fix to reduce the number of rebuilds down by an > factor of 3, but this is still way to much. > > > (That will be ~ 4 total rebuilds) If there is an explanation for this, > fine. > > > > The above is the silliness in how Giraph builds documentation. I'm > > going to tweak > > do-component-build to actually not build docs (since they are not too > useful > > anyway ATM). That should fix it. > > > > > And BTW: Please consider committing BIGTOP-1022 first. > > > > Good point. Will do. > > > > > Otherwise I propose to add an JIRA reading "Remove giraph until build > process is fixed". > > > > Still, what's the JIRA ID for this? > > Evidently, you'd have to create one. > > Cos >
