Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachtest: longer term archiving of artifacts #136302

Open
herkolategan opened this issue Nov 27, 2024 · 1 comment
Open

roachtest: longer term archiving of artifacts #136302

herkolategan opened this issue Nov 27, 2024 · 1 comment
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

Comments

@herkolategan
Copy link
Collaborator

herkolategan commented Nov 27, 2024

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:

  • The test failed
  • It didn't fail because of an infra flake, timeout, or VM preemption
  • Has a small footprint in terms of storage required, for example less than 100MB.
  • A daily / weekly limit of storage has not been reached (could cap the total combined amount from all tests)

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

@herkolategan herkolategan added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-testing Testing tools and infrastructure T-testeng TestEng Team labels Nov 27, 2024
Copy link

blathers-crl bot commented Nov 27, 2024

cc @cockroachdb/test-eng

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant