aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/app/coverage_batch.go
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/app: introduce batch_reproexportTaras Madan2024-10-111-237/+0
| | | | | | | This PR exports the latest reproducer for every bug. Reproducers are exported to the "bug_id/repro_id.c" files. This approach allows to add some metadata files or export more reproducers/bug later. All the files are then archived and uploaded to the preconfigured location.
* dashboard/app: set coverage batching timeout to 12 hoursTaras Madan2024-10-031-4/+1
| | | | | | Sometimes 6 hours are not enough to make the quarter long aggregation. Typically 5 hours 30 minutes are enough. And bonus - delete unused constant.
* dashboard/app: delete unused week->day coverage mergesTaras Madan2024-09-101-83/+1
| | | | Month long merges are the default now.
* dashboard/app: tune coverage update scheduleTaras Madan2024-09-091-9/+22
| | | | | | Quarter long numbers calculation takes 2 hours. Month long numbers calculation takes 15 minutes. Let's update quarters data once per week.
* dashboard/app: branch info is needed to get target commitTaras Madan2024-08-301-5/+6
| | | | | This code was deleted accidentally. Branch information is needed here to get the last target day commit.
* pkg/covermerger: we don't need branch infoTaras Madan2024-08-291-6/+5
| | | | | | | The first versions of this code used branches for git checkout. Later the git repos were merged and branch info usage was reduced. The latest changes switched the code from branch checkout to commit checkout. There is no need in branch info anymore and I don't see any use-cases for it.
* pkg/spanner/coveragedb: move package to pkg/coveragedbTaras Madan2024-08-291-1/+1
|
* dashboard/app: aggregate months and quarters to dbTaras Madan2024-08-291-13/+71
|
* all: fix EnableStorageReadClient errors processingTaras Madan2024-08-141-1/+3
|
* dashboard/app/coverage_batch.go: don't retry even on spotTaras Madan2024-07-261-1/+0
| | | | | | | | | When running on Spot VMs, our batch jobs can get preempted and restarted. For some reason, GCP sometimes starts multiple instances of the same job, which results in duplicate results in the DB. Prevent this by dropping MaxRetryCount. Even if a job fails for a specific day, the data for that day will be processed on the following day, so it does not get lost. If needed, we can manually trigger recalc using /cron/batch_coverage.
* all: make coverage-merger client name configurableTaras Madan2024-07-261-2/+9
|
* dashboard/app: add init scripts for batch processingTaras Madan2024-07-251-7/+13
|
* dashboard/app: support scopes for batch jobsTaras Madan2024-07-251-3/+5
|
* dashboard/app: scale batchingTaras Madan2024-07-051-26/+114
|
* dashboard/app: enable coverage batchingTaras Madan2024-07-051-0/+147