roachtest: longer term archiving of artifacts #136302
Labels
A-testing
Testing tools and infrastructure
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-testeng
TestEng Team
Currently, we only store logs and other debugging info (artifacts) from a roachtest for a limited time on TeamCity.
Once a build reaches a certain age (~1 month) the artifacts are lost.
This issue is a proposal to store the data longer, on cloud storage, in a bucket.
The aim is not to store data for all tests, but rather a subset that has the following properties:
Storing this data would allow us to build up training data for classifying failures.
In the future we should be able to gather all the issues and resulting discussions and combine it with data from the test.
This might be useful to train an LLM to provide assistance during triages.
Proposed solution:
There should be some mechanism that detects the test adhered to the requirements for longer storage. The data should then be backed up to cloud storage and linked to the issue, maybe with a label on the issue indicating that it has been selected for long term storage.
Additional ideas:
Maybe allow adding a label on an issue that will invoke long term storage on that test if done in the initial storage phase. This would require some external process to detect the label and copy the data from TeamCity to longer storage.
Jira issue: CRDB-44966
The text was updated successfully, but these errors were encountered: