[JENKINS-75886] There is already the same child [METHOD] init <0> with the name init in [CLASS]

[jenkins-infra-bot]

When running coverage on a go code with two init functions in the same file (permitted by go, but then they have the same signature), the plugin crashes with the following stack trace : 

org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 4716e9d6-995e-4c9d-b816-9f9065e54c43
java.lang.IllegalArgumentException: There is already the same child [METHOD] init <0> with the name init in [CLASS] - <1, LINE: 0.00% (0/4)>
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.Node.addChild(Node.java:178)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.Node.addChildNode(Node.java:948)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.Node.createMethodNode(Node.java:903)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.createMethodNode(CoberturaParser.java:234)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.createNode(CoberturaParser.java:222)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readClassOrMethod(CoberturaParser.java:164)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readClassOrMethod(CoberturaParser.java:195)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readPackage(CoberturaParser.java:133)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readModule(CoberturaParser.java:112)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.parseReport(CoberturaParser.java:90)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.CoverageParser.parse(CoverageParser.java:81)
	at PluginClassLoader for coverage//io.jenkins.plugins.coverage.metrics.steps.CoverageReportScanner.processFile(CoverageReportScanner.java:63)
	at PluginClassLoader for plugin-util-api//io.jenkins.plugins.util.AgentFileVisitor.scanFiles(AgentFileVisitor.java:114)
	at PluginClassLoader for plugin-util-api//io.jenkins.plugins.util.AgentFileVisitor.invoke(AgentFileVisitor.java:93)
	at PluginClassLoader for plugin-util-api//io.jenkins.plugins.util.AgentFileVisitor.invoke(AgentFileVisitor.java:39)
	at Jenkins v2.479.2//hudson.FilePath$FileCallableWrapper.call(FilePath.java:3614)
	at hudson.remoting.UserRequest.perform(UserRequest.java:225)
	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
	at hudson.remoting.Request$2.run(Request.java:391)
	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:81)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:140)
	at java.base/java.lang.Thread.run(Unknown Source) 

---

Originally reported by vlemaire, imported from: There is already the same child [METHOD] init <0> with the name init in [CLASS]

• assignee: drulli
• status: Open
• priority: Minor
• component(s): coverage-model
• resolution: Unresolved
• votes: 0
• watchers: 3
• imported: 20260108-221235

Raw content of original issue

When running coverage on a go code with two init functions in the same file (permitted by go, but then they have the same signature), the plugin crashes with the following stack trace : 



org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 4716e9d6-995e-4c9d-b816-9f9065e54c43
java.lang.IllegalArgumentException: There is already the same child [METHOD] init <0> with the name init in [CLASS] - <1, LINE: 0.00% (0/4)>
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.Node.addChild(Node.java:178)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.Node.addChildNode(Node.java:948)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.Node.createMethodNode(Node.java:903)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.createMethodNode(CoberturaParser.java:234)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.createNode(CoberturaParser.java:222)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readClassOrMethod(CoberturaParser.java:164)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readClassOrMethod(CoberturaParser.java:195)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readPackage(CoberturaParser.java:133)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.readModule(CoberturaParser.java:112)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.parser.CoberturaParser.parseReport(CoberturaParser.java:90)
	at PluginClassLoader for coverage//edu.hm.hafner.coverage.CoverageParser.parse(CoverageParser.java:81)
	at PluginClassLoader for coverage//io.jenkins.plugins.coverage.metrics.steps.CoverageReportScanner.processFile(CoverageReportScanner.java:63)
	at PluginClassLoader for plugin-util-api//io.jenkins.plugins.util.AgentFileVisitor.scanFiles(AgentFileVisitor.java:114)
	at PluginClassLoader for plugin-util-api//io.jenkins.plugins.util.AgentFileVisitor.invoke(AgentFileVisitor.java:93)
	at PluginClassLoader for plugin-util-api//io.jenkins.plugins.util.AgentFileVisitor.invoke(AgentFileVisitor.java:39)
	at Jenkins v2.479.2//hudson.FilePath$FileCallableWrapper.call(FilePath.java:3614)
	at hudson.remoting.UserRequest.perform(UserRequest.java:225)
	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
	at hudson.remoting.Request$2.run(Request.java:391)
	at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:81)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:140)
	at java.base/java.lang.Thread.run(Unknown Source) 

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  Did you try to set the ignoreErrors property?
  

Did you try to set the ignoreErrors property?

[jenkins-infra-bot]

vlemaire:

• Original comment link
• Raw content of original comment:

  Setting the ignoreParsingErrors property works, issue is no longer present
  

Setting the ignoreParsingErrors property works, issue is no longer present

[jenkins-infra-bot]

mrichar2:

• Original comment link
• Raw content of original comment:

  Encountered this with vite v8 cobertura coverage:
  
  sample:
  
  
  import React from "react";
  
  export const App: React.FC = () => (
    <div>
      <button onClick={() => { console.log("Button One clicked") }}>Button One</button>
      <button onClick={() => { console.log("Button Two clicked") }}>Button Two</button>
    </div>
  );
  
  
  
  <?xml version="1.0" ?>
  <!DOCTYPE coverage SYSTEM "http://cobertura.sourceforge.net/xml/coverage-04.dtd">
  <coverage lines-valid="11" lines-covered="6" line-rate="0.5454" branches-valid="4" branches-covered="3" branch-rate="0.75" timestamp="1754063251582" complexity="0" version="0.1">
    <sources>
      <source>C:/git/mrichar2_tools/v8-coverage</source>
    </sources>
    <packages>
      <package name="main" line-rate="0.5454" branch-rate="0.75">
        <classes>
          <class name="App.tsx" filename="src\App.tsx" line-rate="1" branch-rate="1">
            <methods>
              <method name="App" hits="1" signature="()V">
                <lines>
                  <line number="3" hits="1"/>
                </lines>
              </method>
              <method name="onClick" hits="1" signature="()V">
                <lines>
                  <line number="5" hits="1"/>
                </lines>
              </method>
              <method name="onClick" hits="1" signature="()V">
                <lines>
                  <line number="6" hits="1"/>
                </lines>
              </method>
            </methods>
            <lines>
              <line number="1" hits="1" branch="false"/>
              <line number="3" hits="1" branch="true" condition-coverage="100% (1/1)"/>
              <line number="4" hits="1" branch="false"/>
              <line number="5" hits="1" branch="true" condition-coverage="100% (1/1)"/>
              <line number="6" hits="1" branch="true" condition-coverage="100% (1/1)"/>
              <line number="7" hits="1" branch="false"/>
            </lines>
          </class>
          <class name="index.tsx" filename="src\index.tsx" line-rate="0" branch-rate="0">
            <methods>
              <method name="(empty-report)" hits="0" signature="()V">
                <lines>
                  <line number="1" hits="0"/>
                </lines>
              </method>
            </methods>
            <lines>
              <line number="1" hits="0" branch="true" condition-coverage="0% (0/1)"/>
              <line number="2" hits="0" branch="false"/>
              <line number="3" hits="0" branch="false"/>
              <line number="5" hits="0" branch="false"/>
              <line number="6" hits="0" branch="false"/>
            </lines>
          </class>
        </classes>
      </package>
    </packages>
  </coverage>
  
  
  If there are multiple method blocks perhaps the plugin should assume they are different lambda methods with the same name? If not if this error is encountered the coverage plugin could emit a warning and suggest setting the ignore errors property. It works in the old cobertura plugin so the change in behavior may throw people off during a migration.
  

Encountered this with vite v8 cobertura coverage:

sample:

import React from "react";

export const App: React.FC = () => (
  

     { console.log("Button One clicked") }}>Button One
     { console.log("Button Two clicked") }}>Button Two
  
);

"1.0" ?>
"http://cobertura.sourceforge.net/xml/coverage-04.dtd">
"11" lines-covered="6" line-rate="0.5454" branches-valid="4" branches-covered="3" branch-rate="0.75" timestamp="1754063251582" complexity="0" version="0.1">
  
    C:/git/mrichar2_tools/v8-coverage
  
  
    "main" line-rate="0.5454" branch-rate="0.75">
      
"App.tsx" filename="src\App.tsx" line-rate="1" branch-rate="1">
  
    "App" hits="1" signature="()V">
      
"3" hits="1"/>
      
    
    "onClick" hits="1" signature="()V">
      
"5" hits="1"/>
      
    
    "onClick" hits="1" signature="()V">
      
"6" hits="1"/>
      
    
  
  
    "1" hits="1" branch="false"/>
    "3" hits="1" branch="true" condition-coverage="100% (1/1)"/>
    "4" hits="1" branch="false"/>
    "5" hits="1" branch="true" condition-coverage="100% (1/1)"/>
    "6" hits="1" branch="true" condition-coverage="100% (1/1)"/>
    "7" hits="1" branch="false"/>
  

"index.tsx" filename="src\index.tsx" line-rate="0" branch-rate="0">
  
    "(empty-report)" hits="0" signature="()V">
      
"1" hits="0"/>
      
    
  
  
    "1" hits="0" branch="true" condition-coverage="0% (0/1)"/>
    "2" hits="0" branch="false"/>
    "3" hits="0" branch="false"/>
    "5" hits="0" branch="false"/>
    "6" hits="0" branch="false"/>
  

      
    
  

If there are multiple method blocks perhaps the plugin should assume they are different lambda methods with the same name? If not if this error is encountered the coverage plugin could emit a warning and suggest setting the ignore errors property. It works in the old cobertura plugin so the change in behavior may throw people off during a migration.

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  mrichar2 Did you try to set the ignoreErrors property?
  

mrichar2 Did you try to set the ignoreErrors property?

[jenkins-infra-bot]

[Original duplicates from Jira: JENKINS-72895]

[bopt-agum]

mrichar2 Did you try to set the ignoreErrors property?

I faced this issue too.
Setting Ignore parsing errors during processing of the coverage reports in plug-in configuration helps indeed. At least in my case.

[uhafner]

Which parser and coverage tool do you use? Maybe we can report an issue for the tool so they produce valid coverage files in the future...

[bopt-agum]

Which parser and coverage tool do you use?

gcovr 8.3 to generate cobertura XML output and Cobetura Coverage Reports parser respectively.

Maybe we can report an issue for the tool so they produce valid coverage files in the future...

Sure you may give a try. But I am afraid it could be caused by some specific source code base.