| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Go package names should generally be singular form:
https://go.dev/blog/package-names
https://rakyll.org/style-packages
https://groups.google.com/g/golang-nuts/c/buBwLar1gNw
|
| |
|
|
|
|
| |
New is more idiomatic name and is shorter
(lines where stats.Create is used are usually long,
so making them a bit shorter is good).
|
| | |
|
| | |
|
| |
|
|
|
| |
This will reduce the number of dependencies needed for the main
syzkaller tools.
|
| |
|
|
|
|
| |
VM output we receive on the host is effectively equivalent to RPC recv metric.
If we stop printing programs in the fuzzer, traffic will move from output to RPC.
It will be useful to see this change via metrics.
|
| |
|
|
|
| |
We will also use it to determine when we are ready to schedule programs
that are very likely to crash instances.
|
| |
|
|
|
|
|
| |
Add ability for each package to create and export own stats.
Each stat is self-contained, describes how it should be presented,
and there is not need to copy them from one package to another.
Stats also keep historical data and allow building graphs over time.
|
| |
|
|
|
|
| |
Export first crash time and fix commit hashes.
Export list of managers on which the bug was triggered.
Calculate reporting time more precisely.
|
| |
|
|
|
|
|
|
| |
Building a proper stats analysis tool is definitely out of syzkaller
dashboard's scope.
Delete the code that did not turn out to be useful in practice and
replace it with an export of bug info relevant for statistics.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Enable the user to specify the pivot column for the stats table. If
such a column is set, calculate and print the relative difference
between checkouts and p-values for the estimation of statistical
significance of the experimental data.
For the p-value calculation use the existing implementation from the
go-benchstat tool.
|
|
|
This package will contain generic statistical entities and routies. At
this moment it is mostly needed by syz-testbed.
|