-
Bug
-
Resolution: Unresolved
-
Trivial
-
None
-
HUDSON 1.360 with latest warning plugin
Hi,
I created a very basic hudson project which is checking out 1 single file and compiling it with the following option:
gcc -Wall test.c
with test.c
1 #include <stdio.h> 2 3 int main() 4 { 5 unsigned int i; 6 return 0; 7 }
=> when using warning pluging / gcc parser, it gives me 1 warning which is fine:
File: test.c, Line: 5, Type: gcc, Priority: Normal
unused variable 'i'
Then I add 1 empty line at line 2 and 1 function with 1 new warning at the end of the file (I would be expecting 1 new warning, 2 warnings in total)
01 #include <stdio.h> 02 03 04 int main() 05 { 06 unsigned int i; 07 return 0; 08 } 09 10 int tmp() 11 { 12 unsigned int i; 13 return 0; 14 }
it now gives me:
All Warnings New Warnings Fixed Warnings
2 2 1
With:
Details:
- File: test.c, Line: 6, Type: gcc, Priority: Normal
unused variable 'i' - File: test.c, Line: 12, Type: gcc, Priority: Normal
unused variable 'i'
New:
- File: test.c, Line: 12, Type: gcc, Priority: Normal
unused variable 'i' - File: test.c, Line: 6, Type: gcc, Priority: Normal
unused variable 'i'
Fixed:
File Warning Type
test.c gcc
We only have 1 new warning, and no fixed warning.
So the total is OK, but not the new/fixed count
- blocks
-
JENKINS-61383 Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
- Open
- is duplicated by
-
JENKINS-58403 Issue marked as new when the issue did exist in a previous build but on a different line
- Closed
- is related to
-
JENKINS-24873 Wrong number of new warnings
- Resolved
- relates to
-
JENKINS-61392 Use information from SCM forensics to improve detection of new warnings
- Resolved