Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scoverage plugin for jenkins shows 404 error file not found for some of the scala files but works on some #386

Open
c3-yashgupta opened this issue Nov 1, 2021 · 5 comments

Comments

@c3-yashgupta
Copy link

Scoverage plugin for jenkins shows 404 error file not found for some of the scala files but works with rest. The pattern is kind of random For the files where I am not able to visually see the missing coverage(the html file is missing, dont know why) the corresponding Scoverage.xml file contains the coverage data for that particular file like missing branches etc. Has anybody faced this issue recently or know if it a known bug?

@ckipp01
Copy link
Member

ckipp01 commented Nov 2, 2021

Hi @c3-yashgupta, thanks for the report. What version of the plugin are you using?

@c3-yashgupta
Copy link
Author

Hi @c3-yashgupta, thanks for the report. What version of the plugin are you using?

I am using 1.5.1

@ckipp01
Copy link
Member

ckipp01 commented Nov 2, 2021

Gotcha, any more context about when this is happening or patterns that you can spot will be helpful. To be honest I haven't really looked at the jenkins plugin at all, so I'll add that to the things to look into. It may be a bit as all effort at the moment is going towards getting Scala 3 support it.

@c3-yashgupta
Copy link
Author

Yeah I tried going through the xml file as well to see if there is some difference in the row and root tags. But there is no distinguishing pattern that I could identify. Do you think updating to version 1.9.1 would help?

@ckipp01
Copy link
Member

ckipp01 commented Nov 2, 2021

Possibly. There have been a fair amount of changes since then, especially in the actual scalac-scoverage-plugin. So I'm assuming bumping that will also bring in quite a bit newer of a plugin which may improve some of the reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants