Vites 4.1.11 broke cobertura reports

[dezsiszabi]

Describe the bug

This happened before. At the time it was a bug in ast-v8-to-istanbul. See AriPerkkio/ast-v8-to-istanbul#169

This time I believe it's the change related to the concurrency:

Revive global concurrency limit for test lifecycle [backport to v4] - by @sheremet-va and @hi-ogawa in #10992 (5146d)

I'm speculating of course, but that seems to be the only relevant change.

Now, again, the generated cobertura report xml file contains method names with the same name for the same covered file (for example (anonymous_0) multiple times).

This breaks the cobertura report plugin in Jenkins which expects that the method names are unique. I assume this is mnadated by the cobertura report spec.

Reproduction

I will provide one later, when I'm not on mobile.

System Info

To be shared later.

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @dezsiszabi. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[dezsiszabi]

So far no luck in creating a reproduction. I think the issue might actually be caused by the Angular upgrade I also did at the same time. When I downgrade from @angular/build@22.1.5 to @angular/build@22.1.4, then I don't get duplicate method names in the cobertura report anymore.

Based on the release notes: https://github.com/angular/angular-cli/releases#release-v22.1.5

My guess is the following:

disable code splitting for unit test builds

Commit: angular/angular-cli@b467999

I'll update this thread if I find out more.

[dezsiszabi]

Further confirmation: when i manually change this new flag in angular/angular-cli@b467999#diff-4f4a6414086e1d6fa99280e3e080d31435105983ba42d64f602e5166d935db5dR265 to be false from its default true value, the issue is not happening (even in @angular/build@22.1.5)

[dezsiszabi]

I created a reproduction here with the help of AI:

https://github.com/dezsiszabi/cobertura-bug-repro-2

I will open a ticket on the angular-cli repo as well.

[dezsiszabi]

See related angular-cli issue: angular/angular-cli#33938

[AriPerkkio]

Does this reproduce without Angular? Debugging anything Angular related is pain. 🥲