Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAFKA-2430; Listing of PR commits in commit message should be optional #136

Closed

Conversation

ijuma
Copy link
Contributor

@ijuma ijuma commented Aug 13, 2015

If there is a single commit in the PR, then it's never listed.

@ijuma
Copy link
Contributor Author

ijuma commented Aug 13, 2015

I tested this with PR #99 with both options and #106 to verify a single commit case.

@asfbot
Copy link

asfbot commented Aug 13, 2015

kafka-trunk-git-pr #137 SUCCESS
This pull request looks good

@guozhangwang
Copy link
Contributor

@ijuma It seems contains some irrelevant changes from other JIRAs on ProducerSendThread.scala and CoreUtils.scala.

If there is a single commit in the PR, then it's never listed.
@ijuma ijuma force-pushed the kafka-2430-optional-listing-commits branch from 207ba2e to 64f1aec Compare August 13, 2015 17:30
@ijuma
Copy link
Contributor Author

ijuma commented Aug 13, 2015

Sorry @guozhangwang, it seems like some changes from testing the script were included accidentally (not sure how I didn't see that). Fixed.

@asfgit asfgit closed this in e2ebae8 Aug 13, 2015
@guozhangwang
Copy link
Contributor

Thanks, LGTM!

@asfbot
Copy link

asfbot commented Aug 13, 2015

kafka-trunk-git-pr #138 SUCCESS
This pull request looks good

@ijuma ijuma deleted the kafka-2430-optional-listing-commits branch August 14, 2015 09:48
hachikuji added a commit to hachikuji/kafka that referenced this pull request Feb 28, 2017
hachikuji added a commit to hachikuji/kafka that referenced this pull request Mar 2, 2017
hachikuji added a commit to hachikuji/kafka that referenced this pull request Mar 3, 2017
hachikuji added a commit to hachikuji/kafka that referenced this pull request Mar 9, 2017
hachikuji added a commit to hachikuji/kafka that referenced this pull request Mar 10, 2017
apurvam pushed a commit to apurvam/kafka that referenced this pull request Mar 15, 2017
ijuma pushed a commit to ijuma/kafka that referenced this pull request Mar 22, 2017
hachikuji added a commit to hachikuji/kafka that referenced this pull request Mar 22, 2017
radai-rosenblatt pushed a commit to radai-rosenblatt/kafka that referenced this pull request Apr 22, 2021
TICKET =
LI_DESCRIPTION =
1. For the tests regarding the AlterLogDirs request, When parallelizing the LeaderAndIsr request processing, we disabled the AlterLogDirs request so that they are always rejected. This PR fixes the broken test introduced
by the change.
2. The testMetricsDuringTopicCreateDelete has been flaky, and sometimes fails with a URP count of 1 instead of the expected value 0
3. Not sure why testUnsupportedTLSVersion has been failing on CI, but passing on a local dev box. Disabling it for now.
EXIT_CRITERIA = 
1. If/when we need to re-enable the JBOD features and the AlterLogDirs request.
2 and 3: when these tests are made more robust.
radai-rosenblatt pushed a commit to radai-rosenblatt/kafka that referenced this pull request May 12, 2021
[LI-HOTFIX] Backporting Fixing tests (apache#136)
TICKET =
LI_DESCRIPTION =
This patch adds log for admin client listTopic failure and manually backports some test case changes in 2.4 (apache#136)
1. For the tests regarding the AlterLogDirs request, When parallelizing the LeaderAndIsr request processing, we disabled the AlterLogDirs request so that they are always rejected. This PR fixes the broken test introduced
by the change.
2. The testMetricsDuringTopicCreateDelete has been flaky, and sometimes fails with a URP count of 1 instead of the expected value 0
3. Not sure why testUnsupportedTLSVersion has been failing on CI, but passing on a local dev box. Disabling it for now.
EXIT_CRITERIA = 
1. If/when we need to re-enable the JBOD features and the AlterLogDirs request.
2 and 3: when these tests are made more robust.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants