| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Any is the preferred over interface{} now in Go.
|
| | |
|
| |
|
|
|
| |
This is useful if instances run for different amount of time.
It's hard to make any sense out of aligned records in that case.
|
| | |
|
| | |
|
| |
|
|
|
| |
Move functions that need embed assets to a separate package.
In preparation for the next change.
|
| |
|
|
|
|
|
| |
Add a "syz-repro" target and 3 tables:
- List of all performed (and ongoing) reproductions.
- Comparison of repro rate for different bugs on different checkouts.
- Comparison of the share of C reproducers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Refactor the code of syz-testbed to enable support of different targets.
This required the following changes:
- Instead of doing mass start and mass restart of instances, let them be
more independent.
- Support different types of instances, which may have different
expectations of the target behavior. E.g. syz-manager normally never
exits, while syz-repro is expected to exit after a certain time.
- Factor out stats management, as stat entries may be different for
different targets.
- Introduce locking to TestbedCtx and Checkout, as slices there can be
modified at arbitrary times.
|
| | |
|
| | |
|
| |
|
|
| |
Make it easier to do uiTableType filtering later.
|
| |
|
|
|
| |
This table does not just collect YES/NO, but also shows the number of
test runs in which syz-manager has discovered the given bug.
|
| |
|
|
|
|
|
|
|
| |
Formalise HTML table management - introduce the map, which lists the
available stat tables and their generators.
Render only one page at a time and let the user switch them.
Implement the generation of the bug table.
|
| |
|
|
|
|
| |
Otherwise the page is requested two times by Chrome.
See https://bugs.chromium.org/p/chromium/issues/detail?id=39402
|
| |
|
|
|
|
|
|
|
|
| |
It turns out that we often want to see the data aligned on some specific
property - e.g. align all checkouts by "exec total" and see how other
parameters differ.
Add a preliminary support of such a feature. On a row title click, pick
the minimal value in the row and wind the history of each column back
until the target row value is closest to the minimal one.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
In the HTML form, show only one stat view at a time. Let user switch
between the views.
|
| |
|
|
|
| |
This simplifies table generation and will let us more easily implement
relative difference and p-value calculation and printing.
|
|
|
For now, just display the avg stats and generate graphs on demand.
|
