Skip to content

Add instructions on how to remove master/try artifact data #1701

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

Merged
merged 1 commit into from
Aug 12, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion database/queries.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Useful queries
This document contains useful queries that should be performed manually in exceptional situations.

## Remove data for an artifact from the DB
## Remove data for a stable artifact from the DB
This is important for situations where there is some compilation error for a stable benchmark,
with a stable release of the compiler. While this should be rare, it happens sometimes e.g. because
of future incompatibility lints turning into errors.
Expand All @@ -19,3 +19,17 @@ WHERE name IN ('1.69.0', '1.70.0') AND
type = 'release';
```
After executing this query, the server should automatically re-benchmark these artifacts again.

## Remove data for a master/try artifact from the DB
This is similar to removing a stable artifact, however it also has to be removed from the
`pull_request_build` table.

```sql
DELETE FROM artifact
WHERE name = "<sha>";

DELETE FROM pull_request_build
WHERE bors_sha = "<sha>";
```
After that, the server has to be restarted, or you have to send a GET request to its `/perf/onpush`
endpoint.