[
https://issues.apache.org/jira/browse/KAFKA-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906873#comment-17906873
]
Chia-Ping Tsai commented on KAFKA-18238:
----------------------------------------
I love the idea of leveraging the Gradle API! :)
My script looks like this:
def findStableCommit(start, debounce, depth, command)
This function returns the commit that can successfully execute the specified
command for “debounce” times. The depth parameter determines how many commits
it will attempt to try. The start is the commit we start to try.
Normally, the start is the latest commit on trunk, but Gradle reports can offer
a better “start” to reduce the time of trying unnecessary commits
This approach is simple and expensive, but the returned commit is a good hint
to me. Normally, the next commit is the answer we are looking for.
Just my two cents. Your approach is good to me too, as it seems to seek the
more accurate commit:)
> Identify the first commit where a test became flaky
> ---------------------------------------------------
>
> Key: KAFKA-18238
> URL: https://issues.apache.org/jira/browse/KAFKA-18238
> Project: Kafka
> Issue Type: Sub-task
> Reporter: David Arthur
> Assignee: David Arthur
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
