[JIRA] (JENKINS-60469) Doxygen parser not detecting error

18 views
Skip to first unread message

K.Broselge@gmx.net (JIRA)

unread,
Dec 13, 2019, 1:27:03 AM12/13/19
to jenkinsc...@googlegroups.com
Kevin Broselge created an issue
 
Jenkins / Bug JENKINS-60469
Doxygen parser not detecting error
Issue Type: Bug Bug
Assignee: Ulli Hafner
Components: warnings-ng-plugin
Created: 2019-12-13 06:26
Priority: Minor Minor
Reporter: Kevin Broselge

The new doxygen parser which uses the

Gcc4CompilerParser

does no longer detect errors in "old style".

I assume its from a doxygen subtask (plantUML)

which was detected by the old

DoxygenParser.

 

The error looks like:

Error line 22 in file: C:\projects\Doxygen\html\inline_umlgraph_3.pu

Some diagram description contains errors

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

ullrich.hafner@gmail.com (JIRA)

unread,
Dec 14, 2019, 5:38:02 AM12/14/19
to jenkinsc...@googlegroups.com
Ulli Hafner assigned an issue to Unassigned
Change By: Ulli Hafner
Component/s: analysis-model
Component/s: warnings-ng-plugin
Labels: help-wanted newbie-friendly
Assignee: Ulli Hafner

jarredparrett@gmail.com (JIRA)

unread,
Feb 9, 2020, 7:46:02 PM2/9/20
to jenkinsc...@googlegroups.com
Jarred Parrett assigned an issue to Jarred Parrett
Change By: Jarred Parrett
Assignee: Jarred Parrett

jarredparrett@gmail.com (JIRA)

unread,
Feb 18, 2020, 1:46:03 PM2/18/20
to jenkinsc...@googlegroups.com
Jarred Parrett commented on Bug JENKINS-60469
 
Re: Doxygen parser not detecting error

Hi  Ulli Hafner and Kevin Broselge - I am working on this and have been able to reproduce and narrow it down to more than the patterns contained above. I found the following are picked up by the previous REGEX and not by the present GCC_WARNING_PATTERN as in the GCC4COMPILER.java. In working on this, there seems to be two approaches to fix it. On one hand, the regex could be rewritten to include the necessary missed lines or the two REGEX could be concatenated by way of '|'. There shouldn't be much  - to none - efficiency loss with the concatenation. Can I ask your thoughts on this?

thanks,

Jarred

Contained by DOXYGEN_WARNING_PATTERN and not GCC_WARNING_PATTERN:{{Notice: }}

Output directory `doc/doxygen/framework' does not exist. I have created it for you.

<unknown>:1: Detected potential recursive class relation between class sofa::core::componentmodel::collision::Contact::Factory and base class Factory< std::string, Contact, std::pair< std::pair< core::CollisionModel *, core::CollisionModel * >, Intersection * > >!

<unknown>:-1: Warning: Found unknown command `\TODO'

error: Could not read image `/home/user/myproject/html/struct_foo_graph.png' generated by dot!

 

ullrich.hafner@gmail.com (JIRA)

unread,
Feb 18, 2020, 1:55:02 PM2/18/20
to jenkinsc...@googlegroups.com

The previous regexp caused a lot of exceptions on some input texts, so I needed to remove that parser. If you find a better regexp please go ahead. One way would be to add an additional or to the Gcc regexp. Maybe an even better thing would be to create an additional parser for the missing pieces.

jarredparrett@gmail.com (JIRA)

unread,
Feb 18, 2020, 2:47:02 PM2/18/20
to jenkinsc...@googlegroups.com

Interesting - gotcha I might try my hand at creating a new parser for Doxgen. Do you have any resources you might recommend I take a look at beyond looking at other parser classes? Thank you for the feedback

ullrich.hafner@gmail.com (JIRA)

unread,
Feb 18, 2020, 3:03:02 PM2/18/20
to jenkinsc...@googlegroups.com

No, I think most parsers are a kind of mutation of an existing parser...

Reply all
Reply to author
Forward
0 new messages