[
https://issues.apache.org/jira/browse/KAFKA-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906447#comment-17906447
]
David Arthur edited comment on KAFKA-18238 at 12/17/24 3:43 PM:
----------------------------------------------------------------
You're right [~santhoshct], maybe we should consider a different report for
analyzing a specific test. Generally, what I manually do when looking at a test
is expand to the last 28 days and look for patterns. Has it always been
slightly flaky? Or did it become flaky (or consistently failing) at a certain
point.
We could maybe create a workflow_dispatch GHA that takes in a class and test
name. This report could also display some templates for filing JIRAs and PRs to
mark tests as flaky.
[~chia7712] since you mentioned this, maybe you have some ideas about what
would be useful in terms of heuristics about individual tests.
was (Author: davidarthur):
You're right [~santhoshct], maybe we should consider a different report for
analyzing a specific test. Generally, what I manually do when looking at a test
is expand to the last 28 days and look for patterns. Has it always been
slightly flaky? Or did it become flaky (or consistently failing) at a certain
point.
We could maybe create a workflow_dispatch GHA that takes in a class and test
name. This report could also display some templates for filing JIRAs and PRs to
mark tests as flaky.
> 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)
