PHOENIX-6169 IT suite never finishes on 4.x with HBase 1.3 or 1.4

[stoty]

No description provided.

[stoty]

💔 -1 overall

Vote	Subsystem	Runtime	Comment
+0 🆗	reexec	1m 19s	Docker mode activated.
		_ Prechecks _
+1 💚	dupname	0m 0s	No case conflicting files found.
+1 💚	hbaseanti	0m 0s	Patch does not have any anti-patterns.
+1 💚	@author	0m 0s	The patch does not contain any @author tags.
-1 ❌	test4tests	0m 0s	The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.
		_ 4.x Compile Tests _
+1 💚	mvninstall	10m 31s	4.x passed
+1 💚	compile	1m 20s	4.x passed
+1 💚	checkstyle	0m 41s	4.x passed
+1 💚	javadoc	1m 0s	4.x passed
+0 🆗	spotbugs	3m 58s	phoenix-core in 4.x has 957 extant spotbugs warnings.
		_ Patch Compile Tests _
+1 💚	mvninstall	6m 34s	the patch passed
+1 💚	compile	1m 22s	the patch passed
+1 💚	javac	1m 22s	the patch passed
+1 💚	checkstyle	0m 43s	the patch passed
-1 ❌	shellcheck	0m 0s	The patch generated 2 new + 6 unchanged - 2 fixed = 8 total (was 8)
+1 💚	shelldocs	0m 2s	There were no new shelldocs issues.
+1 💚	whitespace	0m 0s	The patch has no whitespace issues.
+1 💚	javadoc	1m 2s	the patch passed
+1 💚	spotbugs	4m 19s	the patch passed
		_ Other Tests _
-1 ❌	unit	203m 53s	phoenix-core in the patch failed.
+1 💚	asflicense	0m 40s	The patch does not generate ASF License warnings.
		240m 27s

Reason	Tests
Failed junit tests	phoenix.end2end.DropTableWithViewsIT
	phoenix.end2end.OrphanViewToolIT
	phoenix.end2end.ViewIT
	phoenix.query.MaxConcurrentConnectionsIT

Subsystem	Report/Notes
Docker	ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-906/1/artifact/yetus-general-check/output/Dockerfile
GITHUB PR	#906
Optional Tests	dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile shellcheck shelldocs
uname	Linux 91b73c6f91ba 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Build tool	maven
Personality	dev/phoenix-personality.sh
git revision	4.x / b7cb29e
Default Java	Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08
shellcheck	https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-906/1/artifact/yetus-general-check/output/diff-patch-shellcheck.txt
unit	https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-906/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt
Test Results	https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-906/1/testReport/
Max. process+thread count	5697 (vs. ulimit of 30000)
modules	C: phoenix-core U: phoenix-core
Console output	https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-906/1/console
versions	git=2.7.4 maven=3.3.9 shellcheck=0.7.0 spotbugs=4.1.2
Powered by	Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

[ChinmaySKulkarni]

+1, however not sure why it failed the "test4test" when a test was in fact modified. The "test results" url does not point to the correct location either (perhaps a separate jira). Also, @stoty Do we no longer see a test report like we used to before? The "unit" URL points to the console output where you can look for the test results, but the test report view was much more helpful

[stoty]

The test4test problem is probably a Yetus bug, which can be fixed there.
The missing test results should be easily fixed in the config, I'll add a note to PHOENIX-6146.