README.md 9.87 KB
Newer Older
Grant Likely's avatar
Grant Likely committed
1
# EDK2 SCT Results Parser
2

Vincent Stehlé's avatar
Vincent Stehlé committed
3
This is an external parser script for [UEFI SCT]. (WIP)
4

Vincent Stehlé's avatar
Vincent Stehlé committed
5
6
It's designed to read a `.ekl` results log from an [UEFI SCT] run, and a
generated `.seq` from [UEFI SCT] configurator.
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
7

8
It will proceed to generate a Markdown file listing number of failures, passes, each test from the sequence file set that was Silently dropped, and a list of all failures and warnings.
9

Vincent Stehlé's avatar
Vincent Stehlé committed
10
[UEFI SCT]: https://uefi.org/testtools
11

Grant Likely's avatar
Grant Likely committed
12
13
14
15
16
17
18
19
20
21
22
23
24
## Quick Start

If you're using this tool to analyze EBBR test results, use the following
command. The parsed report can be found in `result.md`.

``` {.sh}
$ ./parser.py --config EBBR.yaml \
		</path/to/sct_results/Overall/Summary.ekl> \
		<path/to/sct_results/Sequence/EBBR.seq>
INFO apply_rules: Updated 200 test(s) out of 12206 after applying 124 rule(s)
INFO main: 0 dropped(s), 1 failure(s), 93 ignored(s), 106 known u-boot limitation(s), 12006 pass(s), 0 warning(s)
```

25
## Usage
Vincent Stehlé's avatar
Vincent Stehlé committed
26
Usage to generate a "result md" is such. `python3 parser.py <log_file.ekl> <seq_file.seq>`
27
If you do no provided any command line arguments it will use `sample.ekl` and `sample.seq`.
Vincent Stehlé's avatar
Vincent Stehlé committed
28
The output filename can be specified with `--md <filename>`.
Jeffrey Booher-Kaeding's avatar
Jeffrey Booher-Kaeding committed
29

Vincent Stehlé's avatar
Vincent Stehlé committed
30
An online help is available with the `-h` option.
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
31

32
### Custom search
Vincent Stehlé's avatar
Vincent Stehlé committed
33
For a custom Key:value search, the next two arguments *MUST be included together.* The program will search and display files that met that constraint, without the crosscheck, and display the names, guid, and key:value to the command line. `python3 parser.py <file.ekl> <file.seq> <search key> <search value>`
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
34

Vincent Stehlé's avatar
Vincent Stehlé committed
35
you can use the `test_dict` below to see available keys.
36

Vincent Stehlé's avatar
Vincent Stehlé committed
37
### Sorting data
38

Vincent Stehlé's avatar
Vincent Stehlé committed
39
40
41
It is possible to sort the tests data before output using
the `--sort <key1,key2,...>` option.
Sorting the test data helps when comparing results with diff.
42

Vincent Stehlé's avatar
Vincent Stehlé committed
43
Example command:
44

Vincent Stehlé's avatar
Vincent Stehlé committed
45
46
47
48
``` {.sh}
$ ./parser.py --sort \
      'group,descr,set guid,test set,sub set,guid,name,log' ...
```
49

50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
### Filtering data

The `--filter` option allows to specify a python3 expression, which is used as a
filter. The expression is evaluated for each test; if it evaluates to True the
test is kept, otherwise it is omitted. The expression has access to the test
as dict "x".

Example command, which keeps only the failed tests:

``` {.sh}
$ ./parser.py --filter "x['result'] == 'FAILURE'" ...
```

Filtering takes place after the configuration rules, which are described below.

65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
This filtering mechanism can also be (ab)used to transform tests results.

Example command, which adds a "comment" field (and keeps all the tests):

``` {.sh}
$ ./parser.py \
      --filter "x.update({'comment': 'Transformed'}) or True" ...
```

Example command, which removes filenames prefixes in the "log" field (and keeps
all the tests):

``` {.sh}
$ ./parser.py \
      --filter "x.update({'log': re.sub(r'/.*/', '', x['log'])}) \
                or True" ...
```

83
84
85
86
87
88
89
90
91
92
93
### Keeping only certain fields

Except for the markdown and the config template formats, it is possible to
specify which tests data fields to actually write using the `--fields` option.

Example command, suitable for triaging:

``` {.sh}
$ ./parser.py --fields 'result,sub set,descr,name,log' ...
```

94
The csv format and printing to stdout can retain the fields order.
95

96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
### Collapsing duplicates

It is possible to "collapse" duplicate tests data into a single entry using the
`--uniq` option, much similar in principle to the UNIX `uniq -c` command.

This step happens after tests and fields filtering, and it adds a "count" field.

Example command, suitable for triaging:

``` {.sh}
$ ./parser.py \
      --filter "x.update({'log': re.sub(r'/.*/', '', x['log'])}) \
                or x['result'] != 'PASS'" \
      --fields 'count,result,sub set,descr,name,log' --uniq ...
```

112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
### Printing a summary

It is possible to print results to stdout using the `--print` option. This is
more useful when only few fields are printed. Example command:

Example printing command:

``` {.sh}
$ ./parser.py --fields 'result,name' --print ...
```

More condensed summaries can be obtained with further filtering.

Example summary command:

``` {.sh}
$ ./parser.py \
      --filter "x.update({'log': re.sub(r'/.*/', '', x['log'])}) \
                or x['result'] in ['FAILURE', 'WARNING']" \
      --fields 'count,result,name' --uniq --print ...
```

Vincent Stehlé's avatar
Vincent Stehlé committed
134
135
136
137
138
139
140
## Configuration file

It is possible to use a configuration file with command line option `--config
<filename>`.
This configuration file describes operations to perform on the tests results,
such as marking tests as false positives or waiving failures.

Vincent Stehlé's avatar
Vincent Stehlé committed
141
Example command for [EBBR]:
Vincent Stehlé's avatar
Vincent Stehlé committed
142
143
144
145
146

``` {.sh}
$ ./parser.py --config EBBR.yaml /path/to/Summary.ekl EBBR.seq ...
```

Vincent Stehlé's avatar
Vincent Stehlé committed
147
148
149
150
You need to install the [PyYAML] module for this to work.

[EBBR]: https://github.com/ARM-software/ebbr
[PyYAML]: https://github.com/yaml/pyyaml
Vincent Stehlé's avatar
Vincent Stehlé committed
151
152
153

### Configuration file format

Vincent Stehlé's avatar
Vincent Stehlé committed
154
The configuration file is in [YAML] format. It contains a list of rules:
Vincent Stehlé's avatar
Vincent Stehlé committed
155
156
157
158
159
160
161
162
163
164
165
166
167
168

``` {.yaml}
- rule: name/description (optional)
  criteria:
    key1: value1
    key2: value2
    ...
  update:
    key3: value3
    key4: value4
    ...
- rule...
```

Vincent Stehlé's avatar
Vincent Stehlé committed
169
170
[YAML]: https://yaml.org

Vincent Stehlé's avatar
Vincent Stehlé committed
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
### Rule processing

The rules will be applied to each test one by one in the following manner:

* An attempt is made at matching all the keys/values of the rule's 'criteria'
  dict to the keys/values of the test dict. Matching test and criteria is done
  with a "relaxed" comparison (more below).
  - If there is no match, processing moves on to the next rule.
  - If there is a match:
    1. The test dict is updated with the 'update' dict of the rule.
    2. An 'Updated by' key is set in the test dict to the rule name.
    3. Finally, no more rule is applied to that test.

A test value and a criteria value match if the criteria value string is present
anywhere in the test value string.
For example, the test value "abcde" matches the criteria value "cd".

You can use `--debug` to see more details about which rules are applied to the
tests.

### Sample

A `sample.yaml` configuration file is provided as example, to use with the
`sample.ekl` and `sample.seq` files.

Try it with:

``` {.sh}
$ ./parser.py --config sample.yaml ...
```

202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
### Generating a configuration template

To ease the writing of yaml configurations, there is a `--template` option to
generate a configuration "template" from the results of a run:

``` {.sh}
$ ./parser.py --template template.yaml ...
```

This generated configuration can then be further edited manually.

* Tests with result "PASS" are omitted.
* The following tests fields are omitted from the generated rule "criteria":
  "iteration", "start date" and "start time".
* The generated rule "criteria" "log" field is filtered to remove the leading
  path before C filename.

219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
### EBBR configuration

The `EBBR.yaml` file is a configuration file meant for [EBBR] testing. It can
override the result of some tests with the following ones:

-------------------------------------------------------------------------------
                   Result  Description
-------------------------  ----------------------------------------------------
                `IGNORED`  False-positive test failure, not mandated by [EBBR]
                           and too fine-grained to be removed from the
                           `EBBR.seq` sequence file.

`KNOWN U-BOOT LIMITATION`  Genuine bugs, which much ultimately be fixed.
                           We know about them; they are due to U-Boot FAT
                           filesystem implementation limitations and they do
                           not prevent an OS to boot.
-------------------------------------------------------------------------------

Some of the rules just add a `comments` field with some help text.

Jeffrey Booher-Kaeding's avatar
Jeffrey Booher-Kaeding committed
239
240
## Notes
### Known Issues:
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
241
* "comment" is currently not implemented, as formatting is not currently consistent, should reflect the comments from the test.
Vincent Stehlé's avatar
Vincent Stehlé committed
242
* some [UEFI SCT] tests have shared GUIDs,
243
* some lines in ekl file follow Different naming Conventions
Vincent Stehlé's avatar
Vincent Stehlé committed
244
* some tests in the sequence file are not strongly Associated with the test spec.
245

246
247
248
249
### Documentation

It is possible to convert this `README.md` into `README.pdf` with pandoc using
`make doc`. See `make help`.
250

Vincent Stehlé's avatar
Vincent Stehlé committed
251
252
253
### Sanity checks

To perform sanity checks, run `make check`. For the moment this runs `yamllint`,
Vincent Stehlé's avatar
Vincent Stehlé committed
254
which will inspect all [YAML] files and report errors. See `make help`.
Vincent Stehlé's avatar
Vincent Stehlé committed
255

256
### db structure:
257

Vincent Stehlé's avatar
Vincent Stehlé committed
258
``` {.python}
259
260
261
262
tests = [
    test_dict,
    est_dict2...
]
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
263

264
265
266
267
test_dict = {
   "name": "some test",
   "result": "pass/fail",
   "group": "some group",
Vincent Stehlé's avatar
Vincent Stehlé committed
268
   "test set": "some set",
269
270
271
   "sub set": "some subset",
   "set guid": "XXXXXX",
   "guid": "XXXXXX",
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
272
   "comment": "some comment",
273
274
275
276
   "log": "full log output"
}


Vincent Stehlé's avatar
Vincent Stehlé committed
277
seqs = {
278
279
280
281
282
283
284
285
286
287
    <guid> : seq_dict
    <guid2> : seq_dict2...
}

seq_dict = {
                "name": "set name",
                "guid": "set guid",
                "Iteration": "some hex/num of how many times to run",
                "rev": "some hex/numb",
                "Order": "some hex/num"
Jeff Booher-Kaeding's avatar
V1.0?    
Jeff Booher-Kaeding committed
288
}
289
```
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320

#### Spurious tests

Spurious tests are tests, which were run according to the log file but were not
meant to be run according to the sequence file.

We force the "result" fields of those tests to "SPURIOUS".

#### Dropped tests sets

Dropped tests sets are the tests sets, which were were meant to be run according
to the sequence file but for which no test have been run according to the log
file.

We create artificial tests entries for those dropped tests sets, with the
"result" fields set to "DROPPED". We convert some fields coming from the
sequence file, and auto-generate others:

``` {.python}
dropped_test_dict = {
   "name": "",
   "result": "DROPPED",
   "group": "Unknown",
   "test set": "",
   "sub set": <name from sequence file>,
   "set guid": <guid from sequence file>,
   "revision": <rev from sequence file>,
   "guid": "",
   "log": ""
}
```
321
322
323
324
325
326
327
328

#### Skipped tests sets

Skipped tests sets are the tests sets, which were considered but had zero of
their test run according to the log file.

We create artificial tests entries for those dropped tests sets, with the
"result" fields set to "SKIPPED".