[JENKINS-76183] Coverage plugin runs for 4 minutes without logging any actions?

[jenkins-infra-bot]

---

Originally reported by bgianfo, imported from: Coverage plugin runs for 4 minutes without logging any actions?

• assignee: drulli
• status: Open
• priority: Minor
• component(s): coverage-plugin
• resolution: Unresolved
• votes: 0
• watchers: 3
• imported: 20260107-220949

environment

Jenkins Version: 2.516.3<br/>
Coverage Plugin Version: 2.2941.v08df75b_767f1<br/>
Git Forensics Version: 3.2088.v3a_896f5e4937

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  Are you sure that `git rev-parse` runs as fast as you think?  When you checked the performance, was your performance check in the workspace where the command was executed?
  
  For example, if the workspace is badly in need of garbage collection or is using a network storage device, then it might be very slow.  You could try a `git gc` inside your Pipeline just to see if that helps.
  

Are you sure that `git rev-parse` runs as fast as you think? When you checked the performance, was your performance check in the workspace where the command was executed?

For example, if the workspace is badly in need of garbage collection or is using a network storage device, then it might be very slow. You could try a `git gc` inside your Pipeline just to see if that helps.

[jenkins-infra-bot]

bgianfo:

• Original comment link
• Raw content of original comment:

  Are you sure that `git rev-parse` runs as fast as you think?
  Yes, the same pipeline step runs the same command, and it runs in sub-second time in that case: 
  
  [2025-10-07T21:27:03.328Z]  > git merge fc7d683dab9902788d5880e804739c90671f0bcf # timeout=10
  [2025-10-07T21:27:03.336Z]  > git rev-parse HEAD^{commit} # timeout=10
  [2025-10-07T21:27:03.342Z]  > git config core.sparsecheckout # timeout=10 
  
  

Are you sure that `git rev-parse` runs as fast as you think?

Yes, the same pipeline step runs the same command, and it runs in sub-second time in that case: 

[2025-10-07T21:27:03.328Z]  > git merge fc7d683dab9902788d5880e804739c90671f0bcf # timeout=10
[2025-10-07T21:27:03.336Z]  > git rev-parse HEAD^{commit} # timeout=10
[2025-10-07T21:27:03.342Z]  > git config core.sparsecheckout # timeout=10 

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  Logging the times of the coverage plugin is difficult as some parts are executed on the agent, and some on the controller. The times you see in the console log are the timestamps of the controller.
  
  So it looks like the coloring of the source files takes 4 minutes. You can check this assumption by disabling the source code rendering and looking at the times again. 
  

Logging the times of the coverage plugin is difficult as some parts are executed on the agent, and some on the controller. The times you see in the console log are the timestamps of the controller.

So it looks like the coloring of the source files takes 4 minutes. You can check this assumption by disabling the source code rendering and looking at the times again.