Adar Dembo has posted comments on this change. ( http://gerrit.cloudera.org:8080/10902 )
Change subject: Fix flaky 'Random Backup and Restore' test ...................................................................... Patch Set 1: (3 comments) http://gerrit.cloudera.org:8080/#/c/10902/1//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/10902/1//COMMIT_MSG@20 PS1, Line 20: The above code would produce something withing 1ms of the System within http://gerrit.cloudera.org:8080/#/c/10902/1//COMMIT_MSG@21 PS1, Line 21: Not sure of the root cause, I'd expect the timetamp obtained : from the Kudu client to work. I would too, but only if there were rows actually written; otherwise there'd be no propagated timestamp. Can you double check that the failures weren't all correlated with test runs where the number of rows written were 0? Grant, if you're reading, could you look into this? http://gerrit.cloudera.org:8080/#/c/10902/1/java/kudu-backup/out/test/resources/log4j.properties File java/kudu-backup/out/test/resources/log4j.properties: PS1: What does this file do? I'm asking because it's in a non-standard Maven location (kudu-backup/out/test/resources vs. something like kudu-backup/src/test/sources). -- To view, visit http://gerrit.cloudera.org:8080/10902 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I51a6dbeeb064dff157609fdbbafe505668eb2b26 Gerrit-Change-Number: 10902 Gerrit-PatchSet: 1 Gerrit-Owner: Tony Foerster <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Comment-Date: Tue, 10 Jul 2018 21:09:23 +0000 Gerrit-HasComments: Yes
