[
https://issues.apache.org/jira/browse/PHOENIX-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154630#comment-16154630
]
Hadoop QA commented on PHOENIX-4151:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12885463/PHOENIX-4151_wip_master.patch
against master branch at commit a1c75a9ec31eb646d7f4e0eb2363e8dc6d465103.
ATTACHMENT ID: 12885463
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ admin.split(tableNameBytes,
ByteUtil.concat(Bytes.toBytes(tenantId), Bytes.toBytes("00A" +
Character.valueOf((char) ('3' + nextRunCount()))))); // vary split point with
test run
+ date = new Date(System.currentTimeMillis()), null,
getUrl(), tableDDLOptions);
+
// timestamp
+
// timestamp
+ url = getUrl() + ";" + PhoenixRuntime.CURRENT_SCN_ATTRIB + "=" + (ts +
2) + ";foo=bar"; // Run
+
// query
+
// at
+
// timestamp
+
// timestamp
+ url = getUrl() + ";" + PhoenixRuntime.CURRENT_SCN_ATTRIB + "=" + (ts +
2) + ";foo=bar"; // Run
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.ClientManagedTimeGroupBYIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.QueryIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1375//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1375//console
This message is automatically generated.
> Tests extending BaseQueryIT are flapping
> ----------------------------------------
>
> Key: PHOENIX-4151
> URL: https://issues.apache.org/jira/browse/PHOENIX-4151
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Attachments: PHOENIX-4151.patch, PHOENIX-4151_wip_master.patch,
> PHOENIX-4151_wip.patch
>
>
> Sample failures:
> {code}
> ERROR]
> testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
> at org.apache.phoenix.end2end.NotQueryIT.<init>(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> at org.apache.phoenix.end2end.NotQueryIT.<init>(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s
> (a_integer, a_string) INCLUDE ( B_STRING, A_DATE)
> %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)
> Time elapsed: 0.014 s <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
> at org.apache.phoenix.end2end.QueryIT.<init>(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> at org.apache.phoenix.end2end.QueryIT.<init>(QueryIT.java:66)
> {code}
> {code}
> [ERROR]
> testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
> Time elapsed: 0.007 s <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
> at
> org.apache.phoenix.end2end.CaseStatementIT.<init>(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> at
> org.apache.phoenix.end2end.CaseStatementIT.<init>(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices.
> Probably some sort of a timestamp/scn issue. [~jamestaylor] - any ideas?
> Would injecting our own clock in EnvironmentEdge help?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
