Page History

...

• Check if there are new test failures in Butler that don't yet exist in JIRA (i.e. butler test failures w/out a JIRA link)
• Create JIRA tickets for new failures and link them to the failure entries in Butler
• Keep an eye out for major build infra issues, if some show up hit #cassandra-dev about it
• Optional:
  • Assign test failure JIRA to whomever introduced a new failing test or, if clear, broke an existing stable test
• Hit the #cassandra-dev slack channel for volunteers for any new test failures that show up we can't trivially find attribution for
• Keep an eye on any build infra issues, make sure there are JIRAs created, send email to dev@ notifying about status and progress.
  • (Optional): run a hires config against trunk / other desired branches on circleci, confirm tickets created for failures, create tickets if none

Details

Creating JIRAs

• Create a JIRA ticket with summary: "Test Failures: <suite> <class_name>"
• Set component to the matching "Test/<suite>" component

• Fill out description w/mention of class name and number of failures at time of ticket creation

• In comments, add details of failure w/link to failing run + formatted \{code\} (without \) blocked JIRA capturing output of the test as CI results aren't preserved forever

• After creation, update the ticket to Bug Category "Correctness", "Test Failure"

...