KAFKA-13705: CoreUtils.swallow uses logging parameter instead of Logger #11841
KAFKA-13705: CoreUtils.swallow uses logging parameter instead of Logger #11841Corlobin wants to merge 6 commits intoapache:trunkfrom
Conversation
|
Hi Luke, thanks! I'm taking a look! |
|
Hi @showuon, I believe that is a false-positive, running the spotbugsMain from trunk I receive 6 warnings as described below: spotbugs/spotbugs#1963 I reported a bug on spotbugs and commited the ignore file on I'm waiting a answer from spotbugs repo but I believe ithis s the same false-positive from others spotbugs described in the |
showuon
left a comment
There was a problem hiding this comment.
@Corlobin , thanks for the update. Exclude the SA_FIELD_SELF_COMPARISON looks good to me. But there are failed tests that don't fail in trunk build. Could you help check them?
Build / JDK 8 and Scala 2.12 / kafka.api.PlaintextProducerSendTest.testSendWithInvalidCreateTime()
Build / JDK 8 and Scala 2.12 / kafka.server.ProduceRequestTest.testProduceWithInvalidTimestamp()
ref: https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-11841/4/#showFailuresLink
| some categories of bug reports when using Scala, since spotbugs generates huge | ||
| numbers of false positives in some of these categories when examining Scala code. | ||
|
|
||
| SA_FIELD_SELF_COMPARISON: This method compares a field with itself, and may indicate a typo or a logic error. |
There was a problem hiding this comment.
Thanks for the investigation. I agree it should be false positive. Could we add the spotbugs github issue link here to indicate this should be removed after issue fixed?
There was a problem hiding this comment.
Thanks @showuon , great idea, github issue link added!
|
Thanks @showuon it seems these tests failed appeared on merge of another PR: #11830 after my investigation. Excluded line: https://github.com/apache/kafka/pull/11830/files#r820125170 (as commented) Link error with these tests: https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-11830/3/tests Could you confirm please if was introduced by my PR or was failing before? |
|
Yes, you're right! Those tests are introduced by other PR. However, the recent jenkins build doesn't complete successfully. I've triggered another one to check it. |
|
This PR is being marked as stale since it has not had any activity in 90 days. If you If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact). If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed. |
|
This PR has been closed since it has not had any activity in 120 days. If you feel like this |


As described in the issue, the:
But logging parameter it is never used.
The testing strategy used was to run the
CoreUtilsTestclass and all test projects classes to check if any was broken.Committer Checklist (excluded from commit message)