[
https://issues.apache.org/jira/browse/CASSANDRA-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494980#comment-17494980
]
Michael Semb Wever commented on CASSANDRA-17277:
------------------------------------------------
bq. Notably, the butler run for 940 doesn't show the TestArchiveCommitlog
failure, however in Jenkins if you go to all test failure results for the build
you see it there
I don't get what the intent of this sentence is…
Butler seems to store only 16 builds, and ci-cassandra.a.o stores only 30
builds.
bq. The above output is created by taking the passed in build number and
walking back (and locally caching) the results of all valid previous builds.
This local data is kept in a simple JSON file per branch which we then use for
subsequent calculation of the # of runs we've seen a given test in and the # of
failures; …
This then becomes much more than a cache, it's an important store of history.
We have flakies that are 1:100, well beyond both butlers and ci-cassandra.a.o
history. Also… the challenge that each jenkins agent needs to store its own
cache (and access to it concurrent-safe by both executors) exacerbates because
jobs are sticky to an agent and only get spawned on a new agent when saturation
requires it. That is, every (e.g.) 40 builds could run on a new agent where the
cache needs to be reconstructed but because it cannot fetch anything older than
30 builds that and subsequent commits are going to get associated with past
flakies…
> Automate updating tickets with CI results after merge
> -----------------------------------------------------
>
> Key: CASSANDRA-17277
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17277
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
>
> From [the wiki
> article|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280]
> {quote}ci-cassandra run bot updating ticket in JIRA w/state of test run for
> the SHA (JIRA Pending; to be linked)
> {quote}
> We already run CI for every commit (see
> [example|https://ci-cassandra.apache.org/job/Cassandra-trunk/]). The goal is
> to have automation that'll tie the results of a commit to the original JIRA
> ticket and update it automatically w/a comment indicating:
> * The results of the CI run (duration, pass, fail, # failures)
> * Any potential regressions in CI from the merge w/links to job history
> ([example|https://ci-cassandra.apache.org/job/Cassandra-trunk/912/testReport/junit/dtest.cqlsh_tests.test_cqlsh_copy/TestCqlshCopy/test_bulk_round_trip_with_timeouts/history/])
> From a workflow perspective we want to optimize for having as minimal
> friction as possible to see the impact of one's commit on ci-cassandra and
> rapidly verify if their change appears to have destabilized any tests on that
> infrastructure.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
