[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469874#comment-13469874
]
Hudson commented on HBASE-6784:
---
Integrated in HBase-0.94-security-on-Hadoop-23 #8 (See
[https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/8/])
HBASE-6784 TestCoprocessorScanPolicy is sometimes flaky when run locally
(Revision 1389619)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/util/TestCoprocessorScanPolicy.java
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.2, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13464802#comment-13464802
]
ramkrishna.s.vasudevan commented on HBASE-6784:
---
@Lars
I was thinking that the millisecond diff was not working fine in WINDOWS seeing
HBASE-6833. I have a question here,
Why in Jenkins it has never failed and frequently fails when run in WINDOWS?
Just wanted to know the reason in the delay that happens in the timestamp
updation. Thanks Lars.
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.2, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13464828#comment-13464828
]
Lars Hofhansl commented on HBASE-6784:
--
@Ram:
Most Unix's have good timers (I know Linux has), so it is rare that the two
Puts here receive the same timestamp (but still possible, so the test was still
bad).
The last time I played with timers on Windows I found that the timer resolution
there is about 10ms (but that was many years ago and might be better now).
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.2, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13464844#comment-13464844
]
ramkrishna.s.vasudevan commented on HBASE-6784:
---
Ok Thank you :)
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.2, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13463081#comment-13463081
]
Hudson commented on HBASE-6784:
---
Integrated in HBase-0.94-security #57 (See
[https://builds.apache.org/job/HBase-0.94-security/57/])
HBASE-6784 TestCoprocessorScanPolicy is sometimes flaky when run locally
(Revision 1389619)
Result = SUCCESS
larsh :
Files :
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/util/TestCoprocessorScanPolicy.java
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.2, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13462217#comment-13462217
]
Hudson commented on HBASE-6784:
---
Integrated in HBase-TRUNK #3376 (See
[https://builds.apache.org/job/HBase-TRUNK/3376/])
HBASE-6784 TestCoprocessorScanPolicy is sometimes flaky when run locally
(Revision 1389617)
Result = FAILURE
larsh :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestCoprocessorScanPolicy.java
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.3, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13462232#comment-13462232
]
Hudson commented on HBASE-6784:
---
Integrated in HBase-0.94 #487 (See
[https://builds.apache.org/job/HBase-0.94/487/])
HBASE-6784 TestCoprocessorScanPolicy is sometimes flaky when run locally
(Revision 1389619)
Result = SUCCESS
larsh :
Files :
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/util/TestCoprocessorScanPolicy.java
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.3, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6784) TestCoprocessorScanPolicy is sometimes flaky when run locally
[
https://issues.apache.org/jira/browse/HBASE-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13462264#comment-13462264
]
Hudson commented on HBASE-6784:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #191 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/191/])
HBASE-6784 TestCoprocessorScanPolicy is sometimes flaky when run locally
(Revision 1389617)
Result = FAILURE
larsh :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestCoprocessorScanPolicy.java
TestCoprocessorScanPolicy is sometimes flaky when run locally
-
Key: HBASE-6784
URL: https://issues.apache.org/jira/browse/HBASE-6784
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: Lars Hofhansl
Priority: Minor
Fix For: 0.94.3, 0.96.0
Attachments: 6784.txt
The problem is not seen in jenkins build.
When we run TestCoprocessorScanPolicy.testBaseCases locally or in our
internal jenkins we tend to get random failures. The reason is the 2 puts
that we do here is sometimes getting the same timestamp. This is leading to
improper scan results as the version check tends to skip one of the row
seeing the timestamp to be same. Marking this as minor. As we are trying to
solve testcase related failures just raising this incase we need to resolve
this also.
For eg,
Both the puts are getting the time
{code}
time 1347635287360
time 1347635287360
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
