[JIRA] Commented: (HUDSON-3895) Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-3895) Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140315#action_140315 ]

slide_o_mix commented on HUDSON-3895:
-------------------------------------

Looks like I can't access websites on 8081 from work, so I'll have to download the HPI's from home and email them to myself or something.

> Update warnings plugin to have a generic parser that has a configurable regexp in the Hudson config screen.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-3895
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-3895
>             Project: Hudson
>          Issue Type: New Feature
>          Components: warnings
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: anthonyj
>            Assignee: drulli
>            Priority: Minor
>         Attachments: mylyn-context.zip, mylyn-context.zip
>
>
> 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

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

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