[Issue 3895] New - Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Issue 3895] New - Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

anthonyj
https://hudson.dev.java.net/issues/show_bug.cgi?id=3895
                 Issue #|3895
                 Summary|Update warnings plugin to have a generic parser that h
                        |as a configurable regexp in the Hudson config screen.
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|FEATURE
                Priority|P2
            Subcomponent|warnings
             Assigned to|drulli
             Reported by|anthonyj






------- Additional comments from [hidden email] Fri Jun 19 22:32:54 +0000 2009 -------
One of my customers is a hardware development team and they use some very unique
EDA build tools to do their build.

They would like a complete warnings report of their build. Right now, the
warnings plugin
only finds 2 of their compiler warnings (which happen to be 'GCC like') . I
setup the warnings plugin
to scan the console log and use all parsers. The problem is that the existing
parsers arent picking up all the warnings.
Is there a way to define my own warning parser class? A generic/user-defined
parser option in the parsers
drop-down along with a pattern field in the warnings plugin configuration would
be awesome.

Here are some examples of warning patterns in the build log which the warnings
plugin isnt finding...

#1 warning type not found by plugin

Warning-[TMBIN] Too many bits in Based Number
/projects/mpgIP/users/mpg_hw/sspi/verification/sv/bench/models/i2s/a_codec.v,
780
  The specified width is '12' bits, actually got '16' bits.
  The offending number is : '0000'.
Warning-[UNKWN_IGOPTS] Unknown option(s) ignored
...
Warning-[ENBL_OPTS] Enabling option(s)
...

#2 warning type not found by plugin
***** Warning: +memcbk/-debug* will not enable toggle coverage on MDA please
use -cm_tgl mda to enable it
***** Warning:
file '/projects/mpgIP/users/mpg_hw/sspi/verification/sv/ssp_coverage_config.txt'
 passed with option -cm_hier is nonexistent

#3 warning type not found by plugin
Warning: $fsdbDumpfile - One FSDB file has already opened for dumping.


And here is the Hudson warnings plugin output at the end of the job..

[WARNINGS] Parsing warnings in console log...
[WARNINGS] Found 2 annotations (0 new, 0 high, 2 normal, 0 low)
[WARNINGS] Not changing build status, since no threshold has been exceeded


It found these two and categorized them as GCC which is fine...
/s/flexlm/7.2h/i86_r6/lm_new.c:573: warning: `sys_errlist' is deprecated; use
`strerror' or `strerror_r' instead
/s/flexlm/7.2h/i86_r6/lm_new.c:573: warning: `sys_nerr' is deprecated; use
`strerror' or `strerror_r' instead

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3895] Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

Kohsuke Kawaguchi
Administrator
https://hudson.dev.java.net/issues/show_bug.cgi?id=3895



User kohsuke changed the following:

                What    |Old value                 |New value
================================================================================
                 Summary|Update warnings plugin to |Update warnings plugin to
                        |have a generic parser that|have a generic parser that
                        | has a configurable regexp| has a configurable regexp
                        | in the Hudson config scre| in the Hudson config scre
                        |en.                       |en.
--------------------------------------------------------------------------------




------- Additional comments from [hidden email] Tue Jul 21 23:57:33 +0000 2009 -------
A similar but IMHO better approach is to define the parser as an extension point
to let other plugins contribute parsers. For an example of a plugin defining its
own extension point, see JavaProvider in the ssh-slaves plugin.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3895] Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

anthonyj
In reply to this post by anthonyj
https://hudson.dev.java.net/issues/show_bug.cgi?id=3895






------- Additional comments from [hidden email] Wed Jul 22 00:27:26 +0000 2009 -------
> Sounds good to me Kohsuke.
>
> Electric Commander has something similar where users can add "custom pattern
matchers"
> to their postp.pl script. The custom matchers are stored in a separate file
the is included
> by the main postp.pl script.
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> Sent: Tuesday, July 21, 2009 4:58 PM
> To: [hidden email]
> Subject: [Issue 3895] Update warnings plugin to have a generic parser that has
a configurable regexp in the Hudson config screen.

>
> https://hudson.dev.java.net/issues/show_bug.cgi?id=3895
>
>
>
> User kohsuke changed the following:
>
>                 What    |Old value                 |New value
> ================================================================================
>                  Summary|Update warnings plugin to |Update warnings plugin to
>                         |have a generic parser that|have a generic parser that
>                         | has a configurable regexp| has a configurable regexp
>                         | in the Hudson config scre| in the Hudson config scre
>                         |en.                       |en.
> --------------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3895] Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

drulli
In reply to this post by anthonyj
https://hudson.dev.java.net/issues/show_bug.cgi?id=3895






------- Additional comments from [hidden email] Wed Jul 22 07:40:42 +0000 2009 -------
That would be another approach. However, from a user's perspective it requires
much more work. Entering a new regular expression in the screen requires just a
minute thinking, while writing a new plug-in needs at least a fixed initial
setup of a week or so...

A third alternative would be a configuration screen that provides a Java parser
source code upload method. That could be compiled on the fly with the
JavaCompiler of JDK 6.  

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 3895] Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

anthonyj
In reply to this post by anthonyj
https://hudson.dev.java.net/issues/show_bug.cgi?id=3895






------- Additional comments from [hidden email] Wed Jul 22 16:13:23 +0000 2009 -------
Also, I still think it is important that we give users who are not a java
developer an alternative to specify their regex patterns via the hudson web
interface. Thanks, Anthony

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]