Ok, now I understand. Every warning is contained twice in your log file. Is there a special script that collects the warnings at the tail of the log, or is this the default behavior of the msbuild?

Seems that I already need a set to compute the warnings totals. Currently this is done after that.

Here is the msbuild.log logfile.

I am using the msbuild parser. I will attach one of the log files.

There is only one copy of the msbuild.log file and the search path I use is **/build/msbuild.log

Console log parsing is unchecked.

[WARNINGS] Parsing warnings in files: **/build/msbuild.log
[WARNINGS] Successfully parsed file E:\hudson\jobs\Network Discovery\workspace\KND\build\msbuild.log of module build with 150 warnings.

Those are the only 2 [WARNINGS] lines in the log.

It started happening after I upgraded hudson, but I do not know from which version to which.

Are there any comments from the plug-in in the console log?

E.g.,
[WARNINGS] Parsing warnings in console log...
[WARNINGS] Using set difference to compute new warnings
[WARNINGS] Setting build status to UNSTABLE since total number of annotations exceeds the threshold 0: [HIGH, NORMAL, LOW]

Are you additionally parsing the console log?

Which parsers are you using?

Can you please attach one of the parsed log files (with expected #warnings)?
Is there any chance that the file with the warnings is found twice in your workspace? The plug-in counts the totals based on the found warnings, however the breakdown uses a set which eleminates dplicates.