Re: Updating review board request

Looks like when you squashed the commits you removed the line in the commit message that has a link to the review. It looks like "Review: https://reviews.apache.org/r// ". So, if you manually add that line back to you commit message, post-reviews will update

Re: Updating review board request

I tried running support/post-reviews.py but it creates a new RB request instead of updating existing one.  On Thursday, November 17, 2016 11:37 PM, Vinod Kone wrote: Just run the support/post-reviews.py tool against your rebased branch. It will update the same review on ReviewBoard. O

Re: Updating review board request

Just run the support/post-reviews.py tool against your rebased branch. It will update the same review on ReviewBoard. On Thu, Nov 17, 2016 at 11:27 PM, Vijay Srinivasaraghavan < vijikar...@yahoo.com.invalid> wrote: > Hello, > I have submitted a patch to the Mesos review board using post-reviews.p

Updating review board request

Hello, I have submitted a patch to the Mesos review board using post-reviews.py tool.  I have some changes that I wanted to publish to the same PR. I am not sure if I need to use post-reviews.py or apply-reviews.py tool? The documentation is not clear though it has some reference on addressing fe

Re: [3/3] mesos git commit: Enabled multiple field based authorization in the authorizer interface.

Hi, This introduces a possibly uninitialized member `weight_info` which Coverity immediately detected. I filed MESOS-6604 for that. Could you please take that on @Alexander? Cheers, Benjamin > On Nov 16, 2016, at 6:00 PM, m...@apache.org wrote: > > Enabled multiple field based authorization

Re: Attendance for Mesos Developer Community Meeting (Nov 17)

As it seems that there won't be enough participants, we'll skip this meeting and continue on Dec 1. On Wed, Nov 16, 2016 at 3:25 PM, Joseph Wu wrote: > +0.9 > > Is there an agenda in case there are enough attendees? > > On Wed, Nov 16, 2016 at 3:15 PM, James Peach wrote: > > > > > > On Nov 16,

Re: Build failed in Jenkins: Mesos » autotools,gcc,--verbose --enable-libevent --enable-ssl,GLOG_v=1 MESOS_VERBOSE=1,ubuntu:14.04,(docker||Hadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2) #2933

Hi, >> What do folks think about removing future timeouts in tests altogether? >> Instead, we can time the whole suite differently on different CIs? > Has there been any response from the ASF Infra folks on addressing the > VM/hardware issues? Seems like it will be difficult to get good signal >