| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
If the previous processing terminated in a non-graceful way, the lock
file remains in place and prevents further polls.
|
| |
|
|
|
|
| |
Since remote branches are already mapped to "tree/name" local branches,
there's no need for the special "tree-HEAD" tag anymore. Simplify the
code.
|
| |
|
|
|
| |
Fetch and do build test of the base kernels 3 times per day instead
of 2.
|
| |
|
|
|
| |
It will help better understand lags between the kernel revision used by
syz-cluster and the latest tree commit.
|
| |
|
|
|
|
|
|
| |
Remap remote branches to local ones both when polling remote
repositories and when cloning the distributed repository.
This will ensure that the branches are still accessible via
TreeName/BranchName (it got broken during the latest changes).
|
| |
|
|
| |
Set TTL for the workflow and the pods it creates.
|
| |
|
|
|
| |
When updating the reference kernel repo, first remove the link and then
add it again.
|
| |
|
|
|
| |
Refactor the cron job that pulls the base kernels once in a while to
enable its manual triggering without installing the Argo CLI utility.
|
| |
|
|
|
| |
On GKE, it's the ony option for ReadWriteMany PVC.
Use a custom storage class definition because we use a non-default VPC.
|
| |
|
|
|
| |
Only replace the variables we intended to fix.
This should fix the kernel-disk cron.
|
| |
|
|
|
|
| |
Add another argo workflows cron job that queries Controller for the list
of the trees, mounts the shared kernel repository disk and fetches all
the queried kernel trees.
|
| |
|
|
|
| |
Enable egress traffic for all nodes.
Configure ingress traffic on the per-need basis.
|
|
|
The basic code of a K8S-based cluster that:
* Aggregates new LKML patch series.
* Determines the kernel trees to apply them to.
* Builds the basic and the patched kernel.
* Displays the results on a web dashboard.
This is a very rudimentary version with a lot of TODOs that
provides a skeleton for further work.
The project makes use of Argo workflows and Spanner DB.
Bootstrap is used for the web interface.
Overall structure:
* syz-cluster/dashboard: a web dashboard listing patch series
and their test results.
* syz-cluster/series-tracker: polls Lore archives and submits
the new patch series to the DB.
* syz-cluster/controller: schedules workflows and provides API for them.
* syz-cluster/kernel-disk: a cron job that keeps a kernel checkout up to date.
* syz-cluster/workflow/*: workflow steps.
For the DB structure see syz-cluster/pkg/db/migrations/*.
|