HBASE-22844 Fixed Checkstyle violations in client snapshot exceptions

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
186
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
321
master passed

+1
compile
24
master passed

+1
checkstyle
32
master passed

+1
shadedjars
271
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
21
master passed

0
spotbugs
71
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
70
master passed

_ Patch Compile Tests _

+1
mvninstall
322
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
26
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
262
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
949
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
20
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
68
the patch passed

_ Other Tests _

+1
unit
99
hbase-client in the patch passed.

+1
asflicense
10
The patch does not generate ASF License warnings.

3087

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux e8fcb2deae10 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 8c1edb3bba

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/1/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/1/testReport/

Max. process+thread count
292 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
87
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
360
master passed

+1
compile
29
master passed

+1
checkstyle
38
master passed

+1
shadedjars
313
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
30
master passed

0
spotbugs
82
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
80
master passed

_ Patch Compile Tests _

+1
mvninstall
340
the patch passed

+1
compile
26
the patch passed

+1
javac
26
the patch passed

+1
checkstyle
34
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
299
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1033
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
23
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
85
the patch passed

_ Other Tests _

+1
unit
107
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3301

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 691001005ed6 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / e69af5affe

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/2/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/2/testReport/

Max. process+thread count
264 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
72
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
368
master passed

+1
compile
26
master passed

+1
checkstyle
36
master passed

+1
shadedjars
308
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
26
master passed

0
spotbugs
77
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
75
master passed

_ Patch Compile Tests _

+1
mvninstall
339
the patch passed

+1
compile
26
the patch passed

+1
javac
26
the patch passed

+1
checkstyle
35
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
335
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1275
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
26
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
99
the patch passed

_ Other Tests _

+1
unit
122
hbase-client in the patch passed.

+1
asflicense
15
The patch does not generate ASF License warnings.

3654

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 2752ac5801d2 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 27ed2ac071

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/3/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/3/testReport/

Max. process+thread count
263 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
333
master passed

+1
compile
23
master passed

+1
checkstyle
31
master passed

+1
shadedjars
277
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
22
master passed

0
spotbugs
71
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
70
master passed

_ Patch Compile Tests _

+1
mvninstall
305
the patch passed

+1
compile
24
the patch passed

+1
javac
24
the patch passed

+1
checkstyle
30
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
281
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
964
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
21
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
75
the patch passed

_ Other Tests _

+1
unit
106
hbase-client in the patch passed.

+1
asflicense
11
The patch does not generate ASF License warnings.

2983

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 9f6a6c729385 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 53db390f60

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/4/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/4/testReport/

Max. process+thread count
293 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/4/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
34
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
355
master passed

+1
compile
24
master passed

+1
checkstyle
34
master passed

+1
shadedjars
292
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
23
master passed

0
spotbugs
71
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
68
master passed

_ Patch Compile Tests _

+1
mvninstall
319
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
33
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
291
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1009
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
21
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
73
the patch passed

_ Other Tests _

+1
unit
101
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3105

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 13b03a0e35c0 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / d9d5f69fc6

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/5/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/5/testReport/

Max. process+thread count
263 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/5/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
59
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
384
master passed

+1
compile
26
master passed

+1
checkstyle
32
master passed

+1
shadedjars
299
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
25
master passed

0
spotbugs
72
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
70
master passed

_ Patch Compile Tests _

+1
mvninstall
297
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
30
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
267
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
929
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
20
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
74
the patch passed

_ Other Tests _

+1
unit
99
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3014

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 9e68f7d5aa76 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 8ffc45ab8b

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/6/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/6/testReport/

Max. process+thread count
291 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/6/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
128
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
378
master passed

+1
compile
29
master passed

+1
checkstyle
38
master passed

+1
shadedjars
310
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
25
master passed

0
spotbugs
75
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
73
master passed

_ Patch Compile Tests _

+1
mvninstall
329
the patch passed

+1
compile
27
the patch passed

+1
javac
27
the patch passed

+1
checkstyle
37
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
318
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1232
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
28
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
98
the patch passed

_ Other Tests _

+1
unit
119
hbase-client in the patch passed.

+1
asflicense
15
The patch does not generate ASF License warnings.

3713

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 6c5cc38833ad 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / edf6f68cb2

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/7/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/7/testReport/

Max. process+thread count
261 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/7/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
67
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
432
master passed

+1
compile
33
master passed

+1
checkstyle
42
master passed

+1
shadedjars
357
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
31
master passed

0
spotbugs
94
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
91
master passed

_ Patch Compile Tests _

+1
mvninstall
402
the patch passed

+1
compile
31
the patch passed

+1
javac
31
the patch passed

+1
checkstyle
40
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
372
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1277
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
27
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
101
the patch passed

_ Other Tests _

+1
unit
126
hbase-client in the patch passed.

+1
asflicense
14
The patch does not generate ASF License warnings.

3972

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 8b08c886c723 4.4.0-154-generic #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 60971bee66

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/8/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/8/testReport/

Max. process+thread count
292 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/8/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
37
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
332
master passed

+1
compile
24
master passed

+1
checkstyle
30
master passed

+1
shadedjars
270
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
22
master passed

0
spotbugs
73
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
70
master passed

_ Patch Compile Tests _

+1
mvninstall
301
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
32
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
281
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1018
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
22
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
79
the patch passed

_ Other Tests _

+1
unit
119
hbase-client in the patch passed.

+1
asflicense
15
The patch does not generate ASF License warnings.

3060

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux ce5160f75741 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 78f5d8ebb2

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/9/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/9/testReport/

Max. process+thread count
292 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/9/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
38
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
315
master passed

+1
compile
21
master passed

+1
checkstyle
29
master passed

+1
shadedjars
267
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
21
master passed

0
spotbugs
69
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
66
master passed

_ Patch Compile Tests _

+1
mvninstall
290
the patch passed

+1
compile
26
the patch passed

+1
javac
26
the patch passed

+1
checkstyle
30
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
263
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1066
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
20
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
73
the patch passed

_ Other Tests _

+1
unit
100
hbase-client in the patch passed.

+1
asflicense
11
The patch does not generate ASF License warnings.

2987

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/10/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 9c1aa8bb687f 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 94af65163b

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/10/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/10/testReport/

Max. process+thread count
291 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/10/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
86
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
425
master passed

+1
compile
24
master passed

+1
checkstyle
34
master passed

+1
shadedjars
346
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
28
master passed

0
spotbugs
82
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
79
master passed

_ Patch Compile Tests _

+1
mvninstall
327
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
32
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
323
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1102
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
25
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
91
the patch passed

_ Other Tests _

+1
unit
109
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3445

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/11/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux a6d271e51885 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 3eb602c7f7

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/11/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/11/testReport/

Max. process+thread count
294 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/11/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
245
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
320
master passed

+1
compile
23
master passed

+1
checkstyle
30
master passed

+1
shadedjars
268
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
23
master passed

0
spotbugs
70
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
67
master passed

_ Patch Compile Tests _

+1
mvninstall
299
the patch passed

+1
compile
29
the patch passed

+1
javac
29
the patch passed

+1
checkstyle
30
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
269
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
905
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
20
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
71
the patch passed

_ Other Tests _

+1
unit
98
hbase-client in the patch passed.

+1
asflicense
11
The patch does not generate ASF License warnings.

3059

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/12/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 0bcfcce48278 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 43a0ec80fa

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/12/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/12/testReport/

Max. process+thread count
294 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/12/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
72
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
360
master passed

+1
compile
25
master passed

+1
checkstyle
35
master passed

+1
shadedjars
301
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
22
master passed

0
spotbugs
72
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
69
master passed

_ Patch Compile Tests _

+1
mvninstall
326
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
33
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
299
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1038
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
21
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
75
the patch passed

_ Other Tests _

+1
unit
104
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3220

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/13/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux cc85fca3caba 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 7903f55c18

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/13/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/13/testReport/

Max. process+thread count
265 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/13/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
73
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
358
master passed

+1
compile
24
master passed

+1
checkstyle
34
master passed

+1
shadedjars
298
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
24
master passed

0
spotbugs
72
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
71
master passed

_ Patch Compile Tests _

+1
mvninstall
329
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
34
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
297
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1031
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
21
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
74
the patch passed

_ Other Tests _

+1
unit
102
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3208

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/14/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 71863456abb4 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 8cb531f207

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/14/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/14/testReport/

Max. process+thread count
264 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/14/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
78
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
369
master passed

+1
compile
26
master passed

+1
checkstyle
38
master passed

+1
shadedjars
319
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
26
master passed

0
spotbugs
78
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
76
master passed

_ Patch Compile Tests _

+1
mvninstall
330
the patch passed

+1
compile
27
the patch passed

+1
javac
27
the patch passed

+1
checkstyle
36
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
307
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1040
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
22
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
76
the patch passed

_ Other Tests _

+1
unit
106
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3295

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/15/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 8c99a0638bfe 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 836f26976e

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/15/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/15/testReport/

Max. process+thread count
264 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/15/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
69
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
408
master passed

+1
compile
24
master passed

+1
checkstyle
35
master passed

+1
shadedjars
313
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
24
master passed

0
spotbugs
75
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
73
master passed

_ Patch Compile Tests _

+1
mvninstall
344
the patch passed

+1
compile
29
the patch passed

+1
javac
29
the patch passed

+1
checkstyle
35
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
318
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1067
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
22
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
81
the patch passed

_ Other Tests _

+1
unit
105
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3367

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/16/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux a37538ddb9a2 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 7697d48cd7

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/16/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/16/testReport/

Max. process+thread count
266 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/16/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
95
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
361
master passed

+1
compile
25
master passed

+1
checkstyle
38
master passed

+1
shadedjars
312
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
24
master passed

0
spotbugs
75
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
73
master passed

_ Patch Compile Tests _

+1
mvninstall
356
the patch passed

+1
compile
27
the patch passed

+1
javac
27
the patch passed

+1
checkstyle
36
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
306
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1059
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
22
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
80
the patch passed

_ Other Tests _

+1
unit
104
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3345

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/17/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 98d0b80c34f7 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 46abaef4be

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/17/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/17/testReport/

Max. process+thread count
266 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/17/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
74
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
369
master passed

+1
compile
26
master passed

+1
checkstyle
37
master passed

+1
shadedjars
311
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
35
master passed

0
spotbugs
96
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
93
master passed

_ Patch Compile Tests _

+1
mvninstall
352
the patch passed

+1
compile
26
the patch passed

+1
javac
26
the patch passed

+1
checkstyle
34
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
314
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1070
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
26
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
84
the patch passed

_ Other Tests _

+1
unit
107
hbase-client in the patch passed.

+1
asflicense
13
The patch does not generate ASF License warnings.

3453

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/18/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 11964fada527 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 8e488ce9ef

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/18/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/18/testReport/

Max. process+thread count
265 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/18/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
177
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
355
master passed

+1
compile
26
master passed

+1
checkstyle
31
master passed

+1
shadedjars
325
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
23
master passed

0
spotbugs
77
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
75
master passed

_ Patch Compile Tests _

+1
mvninstall
342
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
30
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
284
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1087
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
21
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
74
the patch passed

_ Other Tests _

+1
unit
103
hbase-client in the patch passed.

+1
asflicense
11
The patch does not generate ASF License warnings.

3405

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/19/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux e547d516bc7b 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 67382809d3

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/19/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/19/testReport/

Max. process+thread count
295 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/19/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
169
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
409
master passed

+1
compile
28
master passed

+1
checkstyle
36
master passed

+1
shadedjars
283
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
24
master passed

0
spotbugs
94
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
85
master passed

_ Patch Compile Tests _

+1
mvninstall
319
the patch passed

+1
compile
23
the patch passed

+1
javac
23
the patch passed

+1
checkstyle
28
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
322
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
953
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1
javadoc
20
hbase-client generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1
findbugs
79
the patch passed

_ Other Tests _

+1
unit
104
hbase-client in the patch passed.

+1
asflicense
13
The patch does not generate ASF License warnings.

3305

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/20/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 44ef2a04058d 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / a59f7d4ffc

Default Java
1.8.0_181

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/20/artifact/out/diff-javadoc-javadoc-hbase-client.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/20/testReport/

Max. process+thread count
290 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/20/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
73
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
363
master passed

+1
compile
27
master passed

+1
checkstyle
38
master passed

+1
shadedjars
271
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
34
master passed

0
spotbugs
103
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
101
master passed

_ Patch Compile Tests _

+1
mvninstall
390
the patch passed

+1
compile
30
the patch passed

+1
javac
30
the patch passed

+1
checkstyle
38
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
352
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1366
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
29
the patch passed

+1
findbugs
95
the patch passed

_ Other Tests _

+1
unit
115
hbase-client in the patch passed.

+1
asflicense
15
The patch does not generate ASF License warnings.

3859

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/21/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 6196fa97e571 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / a59f7d4ffc

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/21/testReport/

Max. process+thread count
263 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/21/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
148
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
375
master passed

+1
compile
32
master passed

+1
checkstyle
37
master passed

+1
shadedjars
283
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
24
master passed

0
spotbugs
81
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
76
master passed

_ Patch Compile Tests _

+1
mvninstall
335
the patch passed

+1
compile
30
the patch passed

+1
javac
30
the patch passed

+1
checkstyle
31
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
278
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
959
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
21
the patch passed

+1
findbugs
76
the patch passed

_ Other Tests _

+1
unit
100
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3198

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/22/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 4b061e742c70 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / ab28f9d8c7

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/22/testReport/

Max. process+thread count
292 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/22/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
88
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
372
master passed

+1
compile
25
master passed

+1
checkstyle
37
master passed

+1
shadedjars
305
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
23
master passed

0
spotbugs
71
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
68
master passed

_ Patch Compile Tests _

+1
mvninstall
336
the patch passed

+1
compile
26
the patch passed

+1
javac
26
the patch passed

+1
checkstyle
34
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
305
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1093
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
22
the patch passed

+1
findbugs
110
the patch passed

_ Other Tests _

+1
unit
114
hbase-client in the patch passed.

+1
asflicense
13
The patch does not generate ASF License warnings.

3397

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/23/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 300bab620aa1 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 66ad42c742

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/23/testReport/

Max. process+thread count
263 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/23/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
87
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
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.

_ master Compile Tests _

+1
mvninstall
367
master passed

+1
compile
25
master passed

+1
checkstyle
35
master passed

+1
shadedjars
308
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
26
master passed

0
spotbugs
75
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
73
master passed

_ Patch Compile Tests _

+1
mvninstall
337
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
34
hbase-client: The patch generated 0 new + 0 unchanged - 13 fixed = 0 total (was 13)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
317
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1075
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
22
the patch passed

+1
findbugs
78
the patch passed

_ Other Tests _

+1
unit
114
hbase-client in the patch passed.

+1
asflicense
12
The patch does not generate ASF License warnings.

3342

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/24/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/487

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 9842efcbb36b 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-487/out/precommit/personality/provided.sh

git revision
master / 7af5b30eca

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/24/testReport/

Max. process+thread count
258 (vs. ulimit of 10000)

modules
C: hbase-client U: hbase-client

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-487/24/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


[Umbrella] Slow integration tests

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the proposal
Some integration tests are taking too long to execute, maybe we can improve them by tweaking configuration, reduce the sleep time, or reduce the workload.
Task list

[ ] Time elapsed: 249.674 s - in org.apache.uniffle.test.LargeSorterTest
[ ] Time elapsed: 239.197 s - in org.apache.uniffle.test.WordCountTest
[ ] Time elapsed: 235.059 s - in org.apache.uniffle.test.SecondarySortTest
[ ] Time elapsed: 174.062 s - in org.apache.uniffle.test.RepartitionWithMemoryRssTest
[ ] Time elapsed: 74.901 s - in org.apache.uniffle.test.ShuffleWithRssClientTest
[ ] Time elapsed: 66.122 s - in org.apache.uniffle.test.RepartitionWithLocalFileRssTest
[ ] Time elapsed: 48.638 s - in org.apache.uniffle.test.QuorumTest
[ ] Time elapsed: 38.97 s - in org.apache.uniffle.test.AQESkewedJoinTest

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

+1. I also doubt whether the mini hdfs startup is the main factor


Add --preview flag for encryptor

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 92.59259% with 2 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

envcloak/utils.py
81.81%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

envcloak/commands/encrypt.py
93.10% <100.00%> (+1.10%)
:arrow_up:

envcloak/utils.py
87.17% <81.81%> (-2.11%)
:arrow_down:


[virtio-fs] Suspected memory leak

Describe the bug
This is a user report received on the Unraid Forums.
To Reproduce
Running VM with virtiofs mappings
Expected behavior
No Memory leakage.
Screenshots

Host:

Disto: Unraid/Opensuse
6.1.63/Unknown
QEMU version 7.2/8.1.2
libvirt version 8.7/Unknown

VM:

Windows version  10/11
Which driver has a problem virtiofs or winfsp
Driver version or commit hash that was used to build the driver see images

Additional context
Mmdi is found in pooltag.txt so you actually have to use xperf and wpa for further debug.  Following the method described there, I captured a snapshot of memory growth, opened it in wpa, loaded symbols, and expanded the Mmdi pool to find stack references to winfsp-x64.dll and virtiofs.exe.  So there's the smoking gun, one of these drivers is the culprit.
I upgraded to the latest versions of WinFSP (2.0) and Virtio-win guest tools (0.1.240) and the leak is still active.

I have been running a Windows 10 guest under KVM for about 1 year now, and I have experienced this memory leak for the entire time.  I am passing through a GPU and a PCIE USB card, and I also mount a few host folders on the guest using VirtioFS. When there is heavy disk I/O on these VioFS folders, the RAM usage of the guest starts increasing rapidly until it eventually reaches 100% and runs out of swap and then crashes. The rate at which the RAM depletes varies with the amount of disk I/O on the VioFS folders. In the worst case (when backup program is running scanning all files), the RAM usage increases about 1M per second and the crash occurs in about 4 hours (16G of RAM allocated to guest). In order for the backup to complete, I have to reboot the guest multiple times to avoid the system crashing.
I found multiple sources that mentioned KVM memory ballooning causes memory leaks when used in combination with GPU passthrough. I set  in the XML config and I disabled blnsvr.exe on the guest. This did not help.
I also tried disabling the virtio serial device. This also did nothing.
I followed Microsoft's guide to track down kernel memory leaks using poolmon. The memory is going to a Non-paged pool with the tag "Mmdi" and the description "MDLs for physical memory allocation".
I provided the debug info in the screenshot above, tracing the Mmdi pool growth to either virtiofs.exe or winfsp-x64.dll.  I can assist with any further debug information required.

@SimonFair Thank you for your report.
Maybe I am missing something, but where is the growth?
BTW: to be a leak, the growth need to be consistent (not jumps, that might be related to temporary allocations).
Can you show "before" and "after" allocation counts? Also what's the amount of memory actually allocated?
I any case, worth investigation.

@YanVugenfirer The growth is consistent while a transfer is occuring. It's in the non paged pool. It can be observed with Poolmon and looking at the Mmdi tag as @christophocles explained. When using backup software it grows extremely quickly and will keep growing until it runs out of memory. Stopping the transfer will not free any memory. Only rebooting the VM will.

@YanVugenfirer here's a screenshot of poolmon showing the kernel memory pool usage after a few hours.  The nonpaged pool Mmdi grows continuously grows, unbounded, until the system crashes.  The growth is accelerated when there is a lot of disk read/write activity on the virtiofs shares.
In the screenshot in the original post, I used Windows Performance Analyzer to trace the processes responsible for the growth of the Mmdi pool.  That was a very time duration, around 30 seconds.  I can run a longer trace if you like.

@christophocles Thanks a lot!
We will take a look and investigate.

I tried to reproduce this issue with the latest rust virtiofsd and virtio driver(242) on Win11 guest, but didn't reproduce it.

Mounted one virtiofs shared dir.
Run fio in the shared dir.
C:\Program Files (x86)\fio\fio\fio.exe" --name=stress --filename=Z:/test_file --ioengine=windowsaio --rw=write --direct=1 --size=1G --iodepth=256 --numjobs=128 --runtime=180000 --thread --bs=64k
Monitor with poolmon.exe, but there was no memory leak.

@SimonFair Could you share what the IO operation in your env? Thanks in advance.

@SimonFair are you using Rust virtiofsd?

@SimonFair are you using Rust virtiofsd?

@YanVugenfirer The bug report originated from my system, and others on the Unraid forums have reported the same issue.  Yes, I am using Rust virtiofsd 1.7.2 which is the version currently packaged on openSUSE Tumbleweed.
@xiagao I am also using virtio-win driver version 0.240 since that is the latest binary release.  I have visual studio and driver toolkits installed so my environment set up to compile newer drivers from source, if needed for testing.  Tonight I will spin up a fresh Win10 VM and try to reproduce the leak again myself, with minimum required steps.  It's possible that other features my specific system are interacting to trigger the memory leak (i.e. PCI-E passthrough?).  If I am able to successfully reproduce the leak on a new VM, I will post detailed steps to reproduce.

@christophocles  @SimonFair

@YanVugenfirer The bug report originated from my system, and others on the Unraid forums have reported the same issue. Yes, I am using Rust virtiofsd 1.7.2 which is the version currently packaged on openSUSE Tumbleweed.

The latest Rust virtiofsd 1.8.0. Please try it.

@kostyanf14 I ran virtiofsd 1.8.0 on Unraid and ran into the same memory leak.

2. C:\Program Files (x86)\fio\fio\fio.exe" --name=stress --filename=Z:/test_file --ioengine=windowsaio --rw=write --direct=1 --size=1G --iodepth=256 --numjobs=128 --runtime=180000 --thread --bs=64k

Where is fio.exe? I only have C:\Program Files\Virtio-Win\VioFS\virtiofs.exe

C:\Program Files (x86)\fio\fio\fio.exe" --name=stress --filename=Z:/test_file --ioengine=windowsaio --rw=write --direct=1 --size=1G --iodepth=256 --numjobs=128 --runtime=180000 --thread --bs=64k

Where is fio.exe? I only have C:\Program Files\Virtio-Win\VioFS\virtiofs.exe

Hi, you can find fio binary in https://fio.readthedocs.io/en/latest/fio_doc.html .

@kostyanf14 I ran virtiofsd 1.8.0 on Unraid and ran into the same memory leak.
Could you share what io test did you do on the shared folder? I also will try some other tools, such as iozone and iometers.

What always does it for me is a free trial of Backblaze Personal Backup and letting it back up my large media library stored on a VirtioFS mount. That will cause Mmdi to grow very quickly.

I should also add I use this batch script to mount several Unraid shares as different drive letters:
"C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsJ Tag1 J:
"C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsl Tag2 l:
"C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsM Tag3 m:
"C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsS Tag4 s:
"C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsT Tag5 T:
I previously ran: C:\Program Files (x86)\WinFsp\bin\fsreg.bat" virtiofs "C:\Program Files\Virtio-Win\VioFS\virtiofs.exe" "-t %%1 -m %%2"

Has anyone been able to repro this?

I reproduced this issue with multiple source mapping from host to Win11 guest. Using IOmeter software to create a lot of disk read/write activity on the virtiofs shares.
Here are some screenshots showing nonpaged pool Mmdi grows continuously after starting IO test and the memory isn't released after stop IO test.

@xiagao I'm glad it's not just us! Thank you for your effort. So hopefully this can eventually be fixed!

Thank you! Can't wait to finally use Virtiofs.

Is there a fix for the issue or has the root cause been found?

@SimonFair not yet. Due to holidays time we are not yet got to debug it.

Just came to report my issue with the memory leaks too.
Running a win11 VM for security cameras writing about 50mbps constantly over virtiofs will chew up my 16gb allocated ram in about 24 hours.
Hope your team had a good holiday period and will look back into this in coming weeks / months for any updates.

It'll be great to know if any progress has been made on this bug?

@mackid1993 No progress due to the holiday season

@kostyanf14 and I found an issue that caused the memory leak (hopefully the only one). Soon CI will build the driver that can be tested if anyone is interested.

@YanVugenfirer Can you please provide a link to the driver once it's been built? Thank you!

Thanks for the update.

I loaded up the new driver from here: https://www.dropbox.com/scl/fo/ssn368eky8yykwwxpuagh/h?rlkey=de69gptabrqi8ihu3x3nakwhu&lst=&dl=0 in test mode and so far so good. I'm going to let some disk activity run overnight but I don't see a leak thus far.
@YanVugenfirer will this fix make it into the next stable release?

I let Backblaze Personal Backup go for a little bit and it seems like the non-paged pool is growing but only when there is virtiofs disk activity. I'm not sure which tag is causing it but here is a screenshot. It seems like there is a much slower leak now.

@YanVugenfirer will this fix make it into the next stable release?

Yes.

I let Backblaze Personal Backup go for a little bit and it seems like the non-paged pool is growing but only when there is virtiofs disk activity. I'm not sure which tag is causing it but here is a screenshot. It seems like there is a much slower leak now.

I am not sure if is this a leak or not. During disk activity, VirtioFS allocates a lot of resources but all of them should be freed when activity stops. Need to check that diff grows between start and stop.

@kostyanf14 It appeared to. When I stopped Backblaze the non-paged pool stopped growing. When I started it again it began to slowly grow. It's better, but I think there may be still a smaller leak.

@YanVugenfirer, thank you for working on this and getting that test driver released for testing, very much appreciated!
@mackid1993 , I also have a Windows VM (Win11) running Backblaze, with it backing up a few TBs of data from over 1/2 a million files.  The Windows OS VM would crash with OOM, after about 6 hours w/o the default Windows OS VM swap (pagefile) during my testing, and roughly a day w/ swap (the default pagefile), but the system would eventually become unresponsive just the same.
I'm now using the recently built driver above in Windows Test Mode (still w/o swap) and it's been backing up for over 13h now w/o issue.  And I see the free memory go up and down, with some of it being released from time to time, which appears to be somewhat corresponding with the release of process handles (presumably Blackblaze threads, but I am not running kernel pool monitor, at this time).  And that makes sense to me and appears to be building confidence of expected behavior.
I did pause the backup and quit the Backblaze control panel, but it did not free memory.  However, that could be due to the service presumably still being loaded and in a paused state ... which I believe is the case, but did not confirm.  So, I am not sure if there is a smaller memory leak or not, or if that's just expected behavior from Backblaze with it holding on to some of the memory in a paused state.
I just set the threads from 8 (default) with automatic throttling, to 20, which has already started using more resources ... I am going to let it run overnight to see what happens, keeping fingers crossed; will provide a brief update tomorrow.

I just set the threads from 8 (default) with automatic throttling, to 20, which has already started using more resources ... I am going to let it run overnight to see what happens, keeping fingers crossed; will provide a brief update tomorrow.

It's still running and memory usage looks good :tada:  I'm going to let it run some more today.  Afterwards, I'll lower RAM to 16GB later today to see if it runs okay over the weekend.

I just set the threads from 8 (default) with automatic throttling, to 20, which has already started using more resources ... I am going to let it run overnight to see what happens, keeping fingers crossed; will provide a brief update tomorrow.

It's still running and memory usage looks good 🎉 I'm going to let it run some more today. Afterwards, I'll lower RAM to 16GB later today to see if it runs okay over the weekend.

Thanks for this. I'm going to test further.

@willdrew How does your non-paged pool look?

I may have to retract my previous statement. This time Backblaze has been going on 100 threads for 2 hours and I'm sitting right here:

I'm going to let it run through tomorrow and report back but I think we are actually looking pretty good.

Thanks for the update.  That's positive to hear and will keep my fingers crossed.  I just bumped my threads to 100 as well, and will let it run for a few hours.  I was already maxing out the bandwidth on the lower threads, but more threads should still push things a bit harder when it comes to memory usage; will report back.

I have mine set like this:

I'm also running 8 VirtioFS mounts right now.

Also, I ended up installing PoolMon, so here's a screenshot sorted by NPaged Usage.

Cool, I've set mine similar.  However, I only have a single VirtioFS mount, which is backed by a 20TB ZFS RAID1 volume with a few zpools  :crossed_fingers:

@willdrew If you're interested in running more mounts I wrote up a couple of batch scripts to simplify that. Here's a link to my post on the Unraid forums: https://forums.unraid.net/topic/129352-virtiofs-support-page/?do=findComment&comment=1301832

I can confirm pausing Backblaze and waiting 10-15 minutes causes non-paged pool memory to be released!

@YanVugenfirer, thank you for working on this and getting that driver built for testing, very much appreciated!
@mackid1993 , all, I also have a Windows VM (Win11) running Backblaze, with it backing up a few TBs of data from over 1/2 a million files. The Windows OS VM would crash with OOM, after about 6 hours w/o the default Windows OS VM swap (pagefile) during my testing, and roughly a day w/ swap (the default pagefile), but the system would eventually become unresponsive just the same. Note, the VM is allocated 32GB of RAM, I will lower this back to 16GB and test this further later, on another day (maybe tomorrow).
I'm now using the recently built driver above in Windows Test Mode (still w/o swap) and it's been backing up for over 13h now w/o issue. And I see the free memory go up and down, with some of it being released from time to time, which appears to be somewhat corresponding with the release of process handles (presumably Blackblaze threads, but I am not running kernel pool monitor, at this time). And that makes sense to me and appears to be building confidence of expected behavior.
I did pause the backup and quit the Backblaze control panel, but it did not free memory. However, that could be due to the service presumably still being loaded and in a paused state ... which I believe is the case, but did not confirm. So, I am not sure if there is a smaller memory leak or not, or if that's just expected behavior from Backblaze with it holding on to some of the memory in a paused state.
I just set the threads from 8 (default) with automatic throttling, to 20, which has already started using more resources ... I am going to let it run overnight to see what happens, keeping fingers crossed; will provide a brief update tomorrow.

Thanls for your testing.

I'm going to let Backblaze chew through 9TB of data over the long weekend and shoot for 48+ hours of uptime but I think this was it!

I'm going to let Backblaze chew through 9TB of data over the long weekend and shoot for 48+ hours of uptime but I think this was it!

Cool, I agree as things are looking quite good on my end as well!

I just bumped my threads to 100 as well, and will let it run for a few hours. I was already maxing out the bandwidth on the lower threads, but more threads should still push things a bit harder when it comes to memory usage; will report back.

It ran fine all day!  Just downgraded the VM to 16GB and will let it run over the long weekend; report back next week.

11 hours of uptime. Backblaze is slowing my 20 core VM with 32 GB of RAM to a crawl it's working so hard (100 threads) and my non paged pool is sitting right here like it was.

@YanVugenfirer When do you think a new release will be created containing this update?

Memory usage is still in a comfortable place with 22 hours of uptime.

@YanVugenfirer When do you think a new release will be created containing this update?

We plan to have a release in a week or two.

@YanVugenfirer When do you think a new release will be created containing this update?

We plan to have a release in a week or two.

That's great. I'm at 29 hours of uptime with a ton of activity on my 8 virtiofs mounts with no issues. I think you fixed it.

@vrozenfe when are  you planning to release upstream version?

The issue was closed automatically due to merger.
Re-opening to keep the discussion open until driver release.

@YanVugenfirer when the upstream version is released will we get a full Virtio driver update or just a signed version of virtofs.sys inf exe etc cetera? Pardon my ignorance.

I started testing the new driver last night, and 14 hours later my RAM usage is stable.  This VM has 4 VioFS mounts backed by 4 zpools, as well as a passthrough GPU and USB3 card.  All seems to be playing nicely together.  Previously, it could barely make it through the file scanning process before OOM and system crash.  This is a massive improvement.  Excellent work, gents!

@YanVugenfirer when the upstream version is released will we get a full Virtio driver update or just a signed version of virtofs.sys inf exe etc cetera? Pardon my ignorance.

In the update we should have the installer with everything.
But keep in mind it is signed by Red Hat, not WHQL singature.

@YanVugenfirer when the upstream version is released will we get a full Virtio driver update or just a signed version of virtofs.sys inf exe etc cetera? Pardon my ignorance.

In the update we should have the installer with everything. But keep in mind it is signed by Red Hat, not WHQL singature.

Does this mean I still have to enable driver test mode?

Does this mean I still have to enable driver test mode?

Previous releases were signed by Red Hat and didn't require test mode.  This test version is completely unsigned which is why the extra steps are needed.  I'd expect the update to be packaged exactly like the previous releases.

Sorry. Meh mistake. It will be MS attestation signature. No need for test mode on Windows 10 and up.

Sorry. My mistake. It will be MS attestation signature. No need for test mode on Windows 10 and up.

Awesome, hopefully it will release soon.

Thanks @mackid1993, @christophocles, all for your testing! Agreed, this is a massive improvement!! :tada:
My final update, TL;DR same as everyone, it's working great! --

I will lower this back to 16GB and test this further later, on another day (maybe tomorrow).

Since late Friday night, I lowered my Windows VM to 16GB and let Backblaze go at it using 100 threads (uploaded about 1TB, due to 40Mbps upload) and it's still running great with no issues (Paged pool 339MB and Non-paged pool 192MB) as of this Tuesday evening!
Thanks again @YanVugenfirer for your hard work on this and looking forward to the official release!

This is awesome, sorry if this has been mentioned in previous threads (this has a long comment history), when will the updated windows ISO's be released?

If you are running on a qemu/libvirt virtual machine, and don't want to test-sign new driver, you may want this as a temp mitigation. This is simply a hot applied version of f604edf. Seems okay on my machine after ~1 hour testing.

@YanVugenfirer When do you think a new release will be created containing this update?

We plan to have a release in a week or two.

Any updates on a release?

If you are running on a qemu/libvirt virtual machine, and don't want to test-sign new driver, you may want this as a temp mitigation. This is simply a hot applied version of f604edf, by modifying the guest's memory directly from host. Seems okay on my machine after ~1 hour testing.

How do you apply this in unraid for instance?

How do you apply this in unraid for instance?

It's probably easier to use the test driver. See my post on the Unraid forum.

@YanVugenfirer Any idea when we'll see a new driver release with this fix? It's been about a month with the test driver and everything is working great.

@YanVugenfirer Any idea when we'll see a new driver release with this fix? It's been about a month with the test driver and everything is working great.

m248 was release a few days ago.

@SimonFair Thanks, just updated.


Ability to select root element type and pass remaining properties to root element

Hello!
I want to user ReactRating component together with styled-components and style root component a little bit. But this is not possible because remaining properties like className are not passed to the root component. Also would be great if there is a possibility to choose root component type.
Great simple project btw :) Cheers!

Solved in #96


VRR/Freesync not working in Gamescope

I have an RX 6700 XT connected to an LG C2 TV over HDMI (should be running at HDMI 2.0 since 2.1 hasn't been sorted out yet). Freesync works in desktop mode when using mutter-vrr and gnome-control-center-vrr packages. I can run vrrtest and see my FPS counter on the TV match what shows on the application. However, in gamescope, Freesync does not work. There's no option in the gui to enable VRR, and adding "export GAMESCOPE_VRR_ENABLED=1" and "--adaptive-sync" to the gamescope command in the gamescope session script hasn't changed anything either. The TV thinks that Freesync Premium is enabled between the PC and the TV, but the FPS counter stays locked to the maximum refresh rate (119). I've tried updating gamescope to gamescope-git and mesa to mesa-git.

I got VRR working with the following changes:

Install gamescope-git
Add --adaptive-sync to GAMESCOPECMD
Change STEAMCMD to "steam -steamos -gamepadui"

Unfortunately this disables a lot of the gamepadui options.
Also, I tried it with Kena: Bridge of Spirits and it makes the smoothness worse. It feels like it's running at half the frame rate or something.
This was my limited testing on a LG C1 and a Radeon RX6800.
Hopefully this can be of use to someone.

I got VRR working with the following changes:

Install gamescope-git
Add --adaptive-sync to GAMESCOPECMD
Change STEAMCMD to "steam -steamos -gamepadui"

Unfortunately this disables a lot of the gamepadui options. Also, I tried it with Kena: Bridge of Spirits and it makes the smoothness worse. It feels like it's running at half the frame rate or something.
This was my limited testing on a LG C1 and a Radeon RX6800.
Hopefully this can be of use to someone.

Can confirm that removing "-steamos3" fixes VRR, but also breaks HDR and a whole lot of other features.

I can confirm the same on the ROG Ally though I'm using gamescope-plus, not gamescope-git.
Was going insane to figure out why VRR wasn't working for me.
Removing -steamos3 works, but removes refresh rate switching, frame rate switching, stops the switch to desktop feature from working, and a whole lot more.
This doesn't seem like a ChimeraOS issue to me, but rather a Gamescope one considering the issue still exists on my pure Arch machine even when using gamescope-git.

I fixed it. You need to add STEAM_GAMESCOPE_VRR_SUPPORTED=1 to the gamescope session script and then enable VRR in the QAM.

Thank you! That fixed it for me too.
For future reference:
To use VRR with stock ChimeraOS create a file $HOME/.config/environment.d/99-vrr.conf with the following content:
STEAM_GAMESCOPE_VRR_SUPPORTED=1
And then reboot/restart session.

It should also be noted that there is a bug in Linux 6.4.x on Radeon 6000 cards where running the monitor at the max refresh with Freesync enabled causes the memory clock to stick at 96 mhz. The workaround is to run the monitor at a lower refresh (100hz works for me).

It should also be noted that there is a bug in Linux 6.4.x on Radeon 6000 cards where running the monitor at the max refresh with Freesync enabled causes the memory clock to stick at 96 mhz. The workaround is to run the monitor at a lower refresh (100hz works for me).

Do you have a bug report link for this?

It should also be noted that there is a bug in Linux 6.4.x on Radeon 6000 cards where running the monitor at the max refresh with Freesync enabled causes the memory clock to stick at 96 mhz. The workaround is to run the monitor at a lower refresh (100hz works for me).

Do you have a bug report link for this?

https://gitlab.freedesktop.org/drm/amd/-/issues/2657

Now I'm running into an issue where VRR doesn't work properly when HDR is enabled. It bounces all over the place even when the framerate is steady.


[ConstraintSystem] Honor -solver-memory-threshold if present.

If the user specifies a memory threshold on the command-line, try to
honor that value and consider expressions too complex if we end up
allocating more memory than they specify.
Fixes rdar://problem/40952582 (aka https://bugs.swift.org/browse/SR-7525).
(cherry picked from commit d135daae4495e268f600e57b156a1f226abb6380)

@swift-ci Please test


Studio Deployment - Helm Chart

Helm Chart to deploy Kubernetes Cluster

Hey @rishabhdas! Thanks for the PR 🚀
We decided to use a separated repository for the helm charts, may you create PR on top of it?
https://github.com/iterative/helm-charts

It looks brilliant 🔥
I guess we need only to make it on top of iterative/helm-charts and merge it

Raised new PR as requested


sync crashing running out of space on /tmp

Describe the bug
I'm trying to sync on the new db version (started with alpha20, and getting the same issue with beta1).
I have plenty of space, just not on /tmp:
df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p5  785G  229G  517G  31% /
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs            16G   42M   16G   1% /dev/shm
tmpfs           6.3G  2.1M  6.3G   1% /run
tmpfs            16G  128M   16G   1% /tmp
/dev/nvme2n1p1  3.6T  2.3T  1.2T  67% /nvme
/dev/sdf2       3.7T 1013G  2.7T  28% /seagate
/dev/nvme0n1p4  984G   36G  898G   4% /home
tmpfs           3.2G   34M  3.1G   2% /run/user/1000

I have no idea what /tmp is being used for. Just intermediate storage during sync, I'd image. If so, I'm guessing there's no startup flag I can use to avoid this. See my startup flags below.
Steps to reproduce
this is my startup script:
# set logging level
logging_level="info,net=error,reth::node::events=error,consensus::engine=debug"

# execute the command
RUST_LOG=$logging_level $command node \
    --log.file.directory ./logs_mainnet \
    --datadir /nvme/reth_mainnet \
    --chain mainnet \
    --http \
    --http.api eth,debug,net,trace,web3,rpc

Node logs
2024-03-08T17:27:35.352146Z  INFO reth::cli: Status connected_peers=5 freelist=1447343 stage=TransactionLookup checkpoint=0 target=19384525 stage_progress=None
2024-03-08T17:27:45.576156Z  INFO reth_node_core::events::node: Forkchoice updated head_block_hash=0x51e127f36756be927cc0bfa510acb1b4f3040358fbc351cd49c6bf2cb71ea114 safe_block_hash=0x2519b014b64b9ed9e105a3aa6c6829b232212bf6e51166b4f4030b81a643cc16 finalize
d_block_hash=0xea91bc916876a0c5cc101ea4ea94a4cff5c39d0969a0ccd37f354aa65e151153 status=Syncing
2024-03-08T17:27:55.548176Z ERROR sync::pipeline: Stage encountered a fatal error: No space left on device (os error 28) at path "/tmp/.tmpwjHJZQ/.tmpqKmTT1" stage=TransactionLookup
2024-03-08T17:27:55.552249Z ERROR reth::cli: shutting down due to error
Error: No space left on device (os error 28) at path "/tmp/.tmpwjHJZQ/.tmpqKmTT1"

Location:
    /rustc/9c3ad802d9b9633d60d3a74668eb1be819212d34/library/core/src/task/poll.rs:255:39

Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.1
Commit SHA: 3c028e5ef
Build Timestamp: 2024-03-08T16:12:50.095325399Z
Build Features: jemalloc
Build Profile: maxperf
previous version I just upgraded from, which gives the same error:
reth Version: 0.1.0-alpha.21
Commit SHA: ef7ce3601
Build Timestamp: 2024-03-02T22:52:35.330153182Z
Build Features: jemalloc
Build Profile: maxperf
What database version are you on?
Current database version: 2
What type of node are you running?
Archive
What prune config do you use, if any?
None, I don't have a reth.toml as far as I'm aware of.
If you've built Reth from source, provide the full command you used
RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf --features jemalloc
Code of Conduct

[X] I agree to follow the Code of Conduct

maybe I should try lowering this
[stages.transaction_lookup]
commit_threshold = 5000000

tried with 10x lower threshold, same error:
2024-03-09T05:38:30.006333Z  INFO reth::cli: Status connected_peers=11 freelist=1250218 stage=TransactionLookup checkpoint=0 target=19391009 stage_progress=None
2024-03-09T05:38:44.000881Z  INFO reth_node_core::events::node: Forkchoice updated head_block_hash=0x1deeef7a6f665dcd1f0dd0d2ae0357ec0768e52aa9813cd9625e1b92b5bab559 safe_block_hash=0x9a1a7f3200224e552c6abd7ec54a2be514187fce8cbc0875a28ec8bcd5154a09 finalized_block_hash=0x3f80f3b822e15c64bfc21d55fdfe59e2136515e9b3a2c5c6ab0463fda4b67d2f status=Syncing
2024-03-09T05:38:44.001494Z DEBUG consensus::engine::hooks: Next hook is not ready hook="StaticFile"
2024-03-09T05:38:55.022284Z  INFO reth::cli: Status connected_peers=13 freelist=1250218 stage=TransactionLookup checkpoint=0 target=19391009 stage_progress=None
2024-03-09T05:39:05.225550Z ERROR sync::pipeline: Stage encountered a fatal error: No space left on device (os error 28) at path "/tmp/.tmpn4fVte/.tmpXcI35L" stage=TransactionLookup
2024-03-09T05:39:05.229117Z ERROR reth::cli: shutting down due to error
Error: No space left on device (os error 28) at path "/tmp/.tmpn4fVte/.tmpXcI35L"

Location:
    /rustc/9c3ad802d9b9633d60d3a74668eb1be819212d34/library/core/src/task/poll.rs:255:39

at commit_threshold = 50000 it doesn't crash, but seems to get stuck:
2024-03-10T00:11:04.752970Z  INFO reth::cli: Status connected_peers=95 freelist=1161867 stage=TransactionLookup checkpoint=0 target=19394124 stage_progress=None
2024-03-10T00:11:29.753743Z  INFO reth::cli: Status connected_peers=89 freelist=1161867 stage=TransactionLookup checkpoint=0 target=19394124 stage_progress=None

You must "reth db drop" to run beta! /tmp is used as scratchspace for our Txlookup and soon hashing stages, it shouldn't cause out of disk. Cc @joshieDo

even if I have reth db version 2? I definitely never ran the drop command. I thought all I had to do was delete my datadir. So I need to start sync from scratch again?

I started from a brand new VM and ran into the same issue, so I can confirm this isn't an issue of alpha leftovers. I'm trying out the transaction lookup config change now.

Unfortunately it didn't take long to hit the same error.
ERROR Stage encountered a fatal error: No space left on device (os error 28) at path "/tmp/.tmpGKyolH/.tmpYaqDtE" stage=Headers
ERROR shutting down due to error
Error: No space left on device (os error 28) at path "/tmp/.tmpGKyolH/.tmpYaqDtE"
Location:
    /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/task/poll.rs:255:39

FYI I am using a datadir that is on a separate volume from the OS. I used the exact same setup using the same resources and I didn't have any issues like this in the alpha.

ACK -- I think this is because /tmp isn't same volume as your datadir. That would make sense. @joshieDo we should P0 fixing this and making tmpfiles from ETL go to datadir.

I confirm successful syncing with beta2