| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Some functions are not the struct members now.
Some functions deleted.
Client mock generated.
|
| |
|
|
|
| |
Let's have a bit more introspection into the asset storage deprecation
code.
|
| | |
|
| | |
|
| |
|
|
|
| |
Fix checking of Logf, it has string in 0-th arg.
Add checking of t.Errorf/Fatalf.
|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
They are stored and handled in a similar way to build assets.
1) syz-manager uploads assets to the storage and reports download URLs
in the /report_crash request.
2) syz-ci manages crash assets deprecation.
3) dashboard includes crash assets in bug reports.
For now the only type is MountInRepro.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
From the upload method, always return the path without the bucket.
Always prepend the bucket name in the downloadURL().
|
| |
|
|
| |
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.
|
|
|
Asset is a file/attachment relevant for debugging a kernel crash or the
syzbot itself.
Dashboard keeps track of the uploaded assets and manages their lifetime.
Some of the assets are attached to the bug reports sent by syzkaller,
some (like html coverage report) are displayed on the web portal.
Two new API requests:
* add_build_assets -- let dashboard remember one more build-related
asset.
* needed_assets -- query the list of assets that are still needed by the
dashboard.
|