-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO
79 lines (50 loc) · 2.03 KB
/
TODO
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
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Triage engine
=============
* Detect hangs.
* Reduced cases are now treated as if the llvm/clang versions don't
affect them (the versions used are stored in the database, but
nothing is done with them, except that when there is a change in a
crash reason, they are removed and thus will be rereduced). Figure
out the right way of using this information.
* Write code to tell apart creduce failure from failure in our
property check script?
* On clang executions, somehow detect a totally botched execution
(like the binary missing). Now it seems to be recorded as a success.
* Locking: Detect that clang_triage is already running for some of the
resources (like the repositories and/or the database).
Database
========
Reducer
=======
* Maybe parallelize the dumb reductions?
* Perhaps split dumb reduce worker from creduce worker? S.t. the dumb
reducer is run for cases where the result in DB is 'creduce_failed'
or something.
* Sometimes CReduce leaves stray clang_delta processes running.
Figure out what can be done about that.
* Investigate why SIGTERMing (Ctrl-c) creduce occasionally results in
a failure to remove the creduce tmpdir, indirectly resulting in
failure to remove the clang_triage tmpdir.
* Do not outright remove outdated reduced cases; mark and show them in
report as possibly outdated.
* Detect new creduce version when deciding to remove/outdate reduced
cases.
Report
======
* Show failed reduces?
* Split report generation: First part queries the DB and outputs JSON,
the other part reads the JSON and generates the report.
* Figure out a better templating engine (for xhtml) than pystache.
* Might make sense to sort creduced cases earlier in report than
dumb-reduced ones?
* Turn output into HTML page, with llvm-symbolizer's locations linked
to some viewer.
Tools
=====
Misc
====
* Also import cases other than those that once crashed, striving for
maximum coverage?
* Also import those of the cases that afl designated as hangs that
actually are hangs.
* Some kind of test framework.