| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
I've got a few weeks worth of data for runs=5 from which
I can check how often time-based values had false negatives.
Let's see if runs=7 performs better (more evenly distributed
between faster and slower), or worse (more likely to get a
super slow result that is otherwise absent).
Change-Id: I38e9b4c2c3c2f4832fc0e9244a00a723510d295f
|
|
|
|
| |
Change-Id: I84a9f1f73b948b57215dfc85ca3242ff1346e8a8
|
|
|
|
| |
Change-Id: I43123d9c001ea59f38f904cd232cb5f8a11e15d8
|
|
|
|
|
|
|
|
|
| |
Per T216854, it's now supported to give the scenarios a name.
This way, the Jenkins build will have headings like "scenario View a page"
instead of "scenario 0", which is difficult to look up or
understand without the config file side-by-side.
Change-Id: If9884c38eef8b05637a8045c4beb3f2bbf8f5de5
|
|
|
|
|
|
|
| |
Also remove unrecognised 'alerts' property from Fresnel config.
That isn't a feature (yet) :)
Change-Id: I45820de67a20c4f0e614b9e845a186f157cab3f4
|
|
Copied from fresnel.git (removed there with I742c56122).
Bug: T133646
Change-Id: I23e7e9bc6343cf9e14dbfe275c1cdbb4cc5bd76d
|