| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| 0/ | H | 25-Apr-2025 | - | 17 | 13 | |
| README.txt | H A D | 25-Apr-2025 | 374 | 8 | 5 | |
| endtime.txt | H A D | 25-Apr-2025 | 18 | 2 | 1 | |
| joblist.txt | H A D | 25-Apr-2025 | 26 | 2 | 1 | |
| metadata.txt | H A D | 25-Apr-2025 | 253 | 14 | 13 | |
| reference.json | H A D | 25-Apr-2025 | 2 KiB | 73 | 73 | |
| starttime.txt | H A D | 25-Apr-2025 | 18 | 2 | 1 | |
| uname.txt | H A D | 25-Apr-2025 | 73 | 2 | 1 |
README.txt
1When --dmesg-warn-level is set to 6 also KERN_INFO level messages should be 2treated as warnings triggering a result change to dmesg-warn/dmesg-fail. 3 4This makes sure that the piglit-style-dmesg does not clash with 5dmesg-warn-level. All the messages are prefixed with drm_ to fit the filters. 6 7IGT messages were artificially bumped to KERN_DEBUG to not pollute the warnings. 8