forked from Pike/e10s_bugs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
53 lines (50 loc) · 1.49 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<!DOCTYPE <!DOCTYPE html>
<html>
<head>
<title>e10s bugs (snapshot)</title>
<link rel="stylesheet" type="text/css" href="bower_components/plottable/plottable.css" />
<script src="bower_components/d3/d3.min.js" charset="utf-8"></script>
<script src="bower_components/plottable/plottable.js" charset="utf-8"></script>
<style>
.axis {
font: 10px sans-serif;
}
.axis path,
.axis line {
fill: none;
stroke: #000;
shape-rendering: crispEdges;
}
.x.axis path {
display: none;
}
.bugLegend {
position: absolute;
right: 0;
bottom: 40;
width: 150px;
}
.bugChart {
position: relative;
}
</style>
</head>
<body>
<h2>e10s bugs, the query</h2>
<p>Below are a few graphs of e10s bugs over time, for a particular
snapshot of the data. The query finds all bugs, that either
<ul>
<li>block a bug with <code>e10s</code> in its alias, or</li>
<li>have a <code>tracking_e10s</code> flag that's none of
<code>?</code>, <code>-</code> or <code>---</code></li>
</ul>
That's a total of <span id="bugcount">?</span> bugs.
</p>
<h2>Reporters</h2>
<p>Unique reporters over time, and per week.</p>
<svg id="reporterChart" width="1000" height="480"></svg>
<h2>Bugs per week</h2>
<p>Bugs reported per week, sliced per e10s trackage and resolution.</p>
<script type="text/javascript" src="javascript/app.js"></script>
</body>
</html>