Feature #10236 ยป Sample_bug_report.txt
1 |
h1. Title |
---|---|
2 |
|
3 |
Title of bug's behavior which should be simple and pithy. |
4 |
|
5 |
|
6 |
h1. Date |
7 |
|
8 |
yyyy/mm/dd |
9 |
|
10 |
|
11 |
h1. Who |
12 |
|
13 |
Specifies your name. |
14 |
|
15 |
|
16 |
h1. Tool version |
17 |
|
18 |
Specify the version number of the Simulator, VIP and so on. |
19 |
|
20 |
|
21 |
h1. CVS/SVN tag |
22 |
|
23 |
Specify the tag number of the CVS/SVN |
24 |
(the release number will be specified if DUT is delivered by the archive.) |
25 |
|
26 |
|
27 |
h1. Bug's category |
28 |
|
29 |
Choose one from ShowStopper, Medium Priority or Low Priority (See the followings) |
30 |
|
31 |
|
32 |
h1. Environment |
33 |
|
34 |
Specify the testbench directory (ex. "TB_XXX_TOP" if the $IP_XXX/src/sv/TB_XXX_TOP is verified) |
35 |
|
36 |
|
37 |
h1. Execution command |
38 |
|
39 |
Specify the execution command when the bug is found. (ex. make bat TEST_MODE=xxx VERI_ITEM=yyy...) |
40 |
|
41 |
|
42 |
h1. Error code number/Error time on waveform |
43 |
|
44 |
Specify the error code number reported by the VIP, the environment and the assertion checkers. |
45 |
If the error code is not shown and no reference in the log file, specify the time point on the waveform. |
46 |
|
47 |
|
48 |
h1. How to confirm this bug |
49 |
|
50 |
Specify the procedure way to confirm this bug. |
51 |
|
52 |
|
53 |
h1. Specification reference |
54 |
|
55 |
Specify the corresponding specification, page, section number and it's title |
56 |
|
57 |
|
58 |
h1. DUT's configuration overview |
59 |
|
60 |
|
61 |
h1. Bug's overview |
62 |
|
63 |
|
64 |
h1. Bug's detail or attachment file( waveform, word, power point, etc )] |