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

Update: Include files with no messages in junit results (#9093) #9094

Merged
merged 1 commit into from Aug 14, 2017
Merged

Update: Include files with no messages in junit results (#9093) #9094

merged 1 commit into from Aug 14, 2017

Conversation

Sean-Der
Copy link
Contributor

@Sean-Der Sean-Der commented Aug 9, 2017

What is the purpose of this pull request? (put an "X" next to item)
[X] Bug fix #9093

What changes did you make? (Give an overview)
Currently when a file has no errors there isn't an entry in the junit results. This breaks some junit parsers as they expect at least one result. It also provides more data since now you know how many files have actually been parsed.

Is there anything you'd like reviewers to focus on?

@eslintbot
Copy link

LGTM

@mention-bot
Copy link

@Sean-Der, thanks for your PR! By analyzing the history of the files in this pull request, we identified @xjamundx, @mysticatea and @kaicataldo to be potential reviewers.

@eslintbot
Copy link

LGTM

@not-an-aardvark not-an-aardvark added bug ESLint is working incorrectly core Relates to ESLint's core APIs and features rule Relates to ESLint's core rules evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion and removed rule Relates to ESLint's core rules labels Aug 9, 2017
Copy link
Member

@not-an-aardvark not-an-aardvark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the pull request!

I'm not very familiar with junit formatters or their expected output, so I can't speak to whether this change is a good idea -- I'll let someone else on the team make that determination. However, assuming that the change is a good idea in general, this implementation looks good to me.

@platinumazure
Copy link
Member

As an aside, it would be so nice if we supported a --formatter-options CLI option where the option could just get passed into the formatter, and then the formatter could actually follow either behavior and the user could decide.

@Sean-Der
Copy link
Contributor Author

Sean-Der commented Aug 9, 2017

Thanks for the review @not-an-aardvark !

@platinumazure I would be more then happy to write that feature! I could see the junit change being controversial, so happy to do whatever makes everyone happy.

@platinumazure
Copy link
Member

platinumazure commented Aug 9, 2017 via email

@not-an-aardvark
Copy link
Member

I'm going to go ahead and accept this because the previous behavior seems like a bug to me, and no one has said otherwise. Thanks again!

@not-an-aardvark not-an-aardvark added accepted There is consensus among the team that this change meets the criteria for inclusion and removed evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion labels Aug 14, 2017
@not-an-aardvark not-an-aardvark merged commit a4f53ba into eslint:master Aug 14, 2017
@Sean-Der Sean-Der deleted the junit-always-output branch August 16, 2017 02:00
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 12, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly core Relates to ESLint's core APIs and features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JUnit formatter should output entry even for files that have no messages
5 participants