The data within brackets can be interpreted as a file name. It gets listed in the file list and the file name is part of what is written inside the brackets.
Tommy Molen
added a comment - Have almost the same problem. In our case it seems like the parsing of output that contains brackets can be misinterpreted.
Typical example:
[junit] <misc junit stdout printout> [data within brackets] [] empty bracket
The data within brackets can be interpreted as a file name. It gets listed in the file list and the file name is part of what is written inside the brackets.
Is this the console message that is parsed? OR the output of the warnings plug-in? I need the exact message from the console log...
Ulli Hafner
added a comment - Is this the console message that is parsed? OR the output of the warnings plug-in? I need the exact message from the console log...
The raw console output from my sample is something like [junit] G GOT < + 120512,21:18:18.005->120512,21:18:18.632 Ab Micid:192.168.0.1 0 2 PEAK_REPORT(3) PSS:12253413403527718 status=NORMAL issi=123456789012345 ssisfn=123456789012 Contexts:[] cpn=mylabs RET=3
Tommy Molen
added a comment - The raw console output from my sample is something like
[junit] G GOT < + 120512,21:18:18.005->120512,21:18:18.632 Ab Micid:192.168.0.1 0 2 PEAK_REPORT(3) PSS:12253413403527718 status=NORMAL issi=123456789012345 ssisfn=123456789012 Contexts:[] cpn=mylabs RET=3
Have almost the same problem. In our case it seems like the parsing of output that contains brackets can be misinterpreted.
Typical example:
[junit] <misc junit stdout printout> [data within brackets] [] empty bracket
The data within brackets can be interpreted as a file name. It gets listed in the file list and the file name is part of what is written inside the brackets.