625
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
1 |
There is a new log filter to generate HTML output. For example,
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
2 |
|
641
|
3 |
sbs --filters=html -f name
|
625
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
4 |
|
641
|
5 |
will produce an output file "name_html/index.html" and other supporting files
|
|
6 |
in the directory "name_html". This can be used alongside the Bz2 filter to
|
625
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
7 |
generate both a human readable summary and a compressed log for further
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
8 |
detailed machine analysis if required: for example,
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
9 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
10 |
sbs --filters=html,bz2log -f name
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
11 |
|
641
|
12 |
will produce a folder "name_html" and a file "name.bz2".
|
625
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
13 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
14 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
15 |
If a build is done in several parts, for example,
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
16 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
17 |
sbs -s sys1.xml --filters=html,bz2log -f build/part1
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
18 |
sbs -s sys2.xml --filters=html,bz2log -f build/part2
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
19 |
sbs -s sys3.xml --filters=html,bz2log -f build/part3
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
20 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
21 |
Then there is a new script "SBS_HOME/bin/sbs_index.py" which can produce a
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
22 |
single index linking to all the individual parts: for example,
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
23 |
|
641
|
24 |
sbs_index.py build/part{1,2,3}_html build/index.html
|
625
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
25 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
26 |
the first parameters are the directories to search for summaries and the
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
27 |
last parameter is the name of the overall index file. Directories are
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
28 |
searched recursively, so the above example is the same as,
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
29 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
30 |
sbs_index.py build build/index.html
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
31 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
32 |
|
641
|
33 |
Text in the Raptor logs is classified as Error, Critical, Warning or Remark
|
|
34 |
using the list of regular expressions in the file,
|
|
35 |
|
|
36 |
SBS_HOME/lib/config/logfile_regex.csv
|
|
37 |
|
625
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
38 |
but this can be overriden by placing a file of the same name in the kit in
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
39 |
its EPOCROOT/epoc32/sbs_config folder.
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
40 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
41 |
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
42 |
The filter also checks that all the files which were listed in "what" output
|
Richard Taylor <richard.i.taylor@nokia.com>
parents:
diff
changeset
|
43 |
actually exist at the end of the build. Any files which don't exist are
|
641
|
44 |
recorded as "Missing files".
|
|
45 |
|
|
46 |
|
|
47 |
Sometimes when a target cannot be built you will see errors like this in the
|
|
48 |
HTML report,
|
|
49 |
"
|
|
50 |
/opt/nokia/wk99/epoc32/build/something
|
|
51 |
|
|
52 |
required the following files which could not be found,
|
|
53 |
|
|
54 |
/opt/nokia/wk99/epoc32/include/foo
|
|
55 |
/opt/nokia/wk99/epoc32/include/bar
|
|
56 |
"
|
|
57 |
|
|
58 |
which means that a dependency was created on "foo" and "bar" but the build
|
|
59 |
did not contain any information anywhere on how to build those files. This
|
|
60 |
is often caused by someone just forgetting to add files to the asset.
|
|
61 |
|