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

fail to run reviewdog: XML syntax error on line 10: expected attribute name in element #1612

Open
niladrix719 opened this issue Nov 19, 2023 · 1 comment

Comments

@niladrix719
Copy link

reviewdog: fail to run reviewdog: XML syntax error on line 10: expected attribute name in element
Error: Process completed with exit code 1.

i am getting this error on my test ci , but i think its not a issue with my PR

https://github.com/CircuitVerse/CircuitVerse/actions/runs/6919019376/job/18821894314?pr=3923

@dgholz
Copy link

dgholz commented May 9, 2024

@niladrix719 I see that you recreated your PR and it ran fine. That error from reviewdog:

XML syntax error on line 10: expected attribute name in element

indicates it was asked to parse XML, but was passed differently-formatted text. Perhaps the output from bundle exec undercover-checkstyle -c origin/master included some error logging, but reviewdog ate it & so you didn't see it.

The -tee option is very helpful in these cases, as reviewdog will echo out what it was passed. You could add this to your Run reviewdog step definition in .github/workflows/rubyonrails.yml. If you want to revisit a 6-month old PR… reviewdog has had a few releases since then (it was v0.15.0), but hasn't had any significant changes to how it parses XML.

I managed to get a similar error out of reviewdog when my Bundler setup was crummy, and bundle exec printed extra logging. So my guess is that the cache from the ruby/setup-ruby action was corrupted somehow? Quite difficult to tell without the logs from the run.

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

No branches or pull requests

2 participants