Re: [DISCUSS] Test monitoring process and rotation

2016-10-04 Thread Li Li
The current test status is actually a very important factor to explain why the monitoring process and rotation is necessary, and help to decide how the monitoring process should be. Also does it include both the master and feature branch (e.g. sentry-ha-redesign)? On Tue, Oct 4, 2016 at 1:55 PM,

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

2016-10-04 Thread Hao Hao
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52138/ --- (Updated Oct. 4, 2016, 11:18 p.m.) Review request for sentry, Alexander Kolbaso

Re: Review Request 45859: SENTRY-1120: Show role / privileges info in Sentry Service Webpage

2016-10-04 Thread Li Li
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45859/ --- (Updated Oct. 4, 2016, 10:23 p.m.) Review request for sentry, Alexander Kolbaso

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

2016-10-04 Thread Hao Hao
> On Sept. 23, 2016, 4:41 p.m., Alexander Kolbasov wrote: > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java, > > lines 239-257 > > > > > > Are there any establish

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

2016-10-04 Thread Hao Hao
> On Sept. 24, 2016, 11:59 p.m., Alexander Kolbasov wrote: > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java, > > lines 215-216 > > > > > > fullUpdateComplete var

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

2016-10-04 Thread Hao Hao
> On Oct. 4, 2016, 6:44 a.m., Alexander Kolbasov wrote: > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/ServiceConstants.java, > > lines 130-135 > > > > > > So this isn't actual

Re: [DISCUSS] Test monitoring process and rotation

2016-10-04 Thread Sravya Tirukkovalur
That is exactly why I think a process might be useful. I dont believe we have a clear way to answer that question of "What is the current test status? What are current known issues? And how are we making progress towards no flakyness?" At least not that I know of. One of us can spend some time loo

Re: [DISCUSS] Test monitoring process and rotation

2016-10-04 Thread Li Li
It is better if we can get some idea about the current test status, like how many known or unknown flaky tests, which tests are disabled and with what reason, any existing jiras tracking these failure tests. Also does it include both the master and feature branch? On Tue, Oct 4, 2016 at 1:28 PM,

Review Request 52526: SENTRY-1477: Sentry clients should retry with another server when they get connection errors

2016-10-04 Thread Li Li
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52526/ --- Review request for sentry, Alexander Kolbasov, Anne Yu, Hao Hao, and Sravya Tiru

[DISCUSS] Test monitoring process and rotation

2016-10-04 Thread Sravya Tirukkovalur
Hi all, As the project grows, I think it might be useful to have a process and rotation of responsibility on how we maintain the health of test runs which is a crucial piece in project health. I documented a draft of the process, please provide your inputs if you think it would be useful also ple