File: error_parsers.txt

package info (click to toggle)
khronos-opencl-clhpp 3.0~2023.02.06-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 5,640 kB
  • sloc: ansic: 26,445; cpp: 9,958; ruby: 9,564; tcl: 2,925; pascal: 2,280; makefile: 311; python: 220; asm: 133; sh: 20
file content (26 lines) | stat: -rw-r--r-- 1,138 bytes parent folder | download | duplicates (9)
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
Eclipse error parsers
=====================

These are a godsend for extracting  & quickly navigating to
warnings & error messages from console output. Unforunately
I don't know how to write an Eclipse plugin so you'll have
to add them manually.

To add a console parser to Eclipse, go to Window --> Preferences
--> C/C++ --> Build --> Settings. Click on the 'Error Parsers'
tab and then click the 'Add...' button. See the table below for
the parser fields to add.

Eclipse will only parse the console output during a build, so
running your unit tests must be part of your build process.
Either add this to your make/rakefile, or add it as a post-
build step in your Eclipse project settings.


Unity unit test error parsers
-----------------------------
Severity    Pattern                                 File    Line    Description
-------------------------------------------------------------------------------
Error       (\.+)(.*?):(\d+):(.*?):FAIL: (.*)       $2      $3      $5
Warning     (\.+)(.*?):(\d+):(.*?):IGNORE: (.*)     $2      $3      $5
Warning     (\.+)(.*?):(\d+):(.*?):IGNORE\s*$       $2      $3      Ignored test