HI All, It looks like our build (which was pretty close to 60 minutes total build time) has finally gone over the timeout threshold on builds.apache.org. In the short term, is there someone with permissions to edit the build jobs and increase the timeout?
It looks like it crept up over a few different builds: https://builds.apache.org/job/Ambari-trunk-Commit/1323 Ambari Server ..................................... SUCCESS [45:33 min] https://builds.apache.org/job/Ambari-trunk-Commit/1324 Ambari Server ..................................... SUCCESS [48:21 min] Increase of 3 minutes AMBARI-8808. Resolve potential port conflicts with Hadoop daemons. alerts.json default port change. (swage) https://builds.apache.org/job/Ambari-trunk-Commit/1325 Ambari Server ..................................... SUCCESS [54:26 min] Increase of 6 minutes Revert "AMBARI-8872. Support point in time queries. Breaks dashboard graphs." (detail / gitweb AMBARI-8869. Include AMS debian packages in Ambari build. (mpapirkovskyy) (detail / gitweb) I’m guessing AMBARI-8869 is causing this. If new packages are being built, I’m surprised it takes 6 minutes. In any event, we should probably increase the job timeout. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
