| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Let's have a bit more introspection into the asset storage deprecation
code.
|
| | |
|
| |
|
|
| |
Define a pkg-only view of the required dashapi methods.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
If several syz-cis with different GCS buckets for assets are connected
to a single dashboard, we currently face problems during the asset
deprecation process.
If we receive from the dashboard a valid GCS URL that belong to an
unknown bucket, don't abort the process. Just ignore the URL.
Test this behavior.
|
| |
|
|
|
| |
Collect mounted images from repros and upload them to the asset
storage. Report the resulting download URLs to the dashboard.
|
| |
|
|
|
|
|
|
| |
It causes web browsers to decompress archives in place, which makes it
more confusing for the users since the file extension remains in place.
The only exception is html coverage reports, adjust the code to handle
that.
|
| |
|
|
| |
The caller expects a FileExistsError error.
|
| |
|
|
|
| |
Calculate sha256 values of assets-to-upload and don't upload them if
they already exist.
|
| |
|
|
|
| |
Calling an external tool imposes multiple OS/version compatibility
issues.
|
|
|
This commit introduces the syz-ci side of the asset storage
functionality.
* Intercept assets at various stages of syz-ci operation.
* Compress and upload assets to GCS.
* Report assets to the dashboard.
* Remove no longer needed assets.
|