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

Can't see details of failed tests #3

Closed
vmassol opened this issue Apr 25, 2020 · 4 comments
Closed

Can't see details of failed tests #3

vmassol opened this issue Apr 25, 2020 · 4 comments

Comments

@vmassol
Copy link

@vmassol vmassol commented Apr 25, 2020

Thank you for your tool!

I’m currently exploring GitHub Actions and trying your tool. It seems promising and right now there doesn’t seem to be a lot of options in GitHub Actions to see junit test results! :)

I’ve tried it on some xwiki repo and got this result: https://github.com/vmassol/xwiki-commons/runs/618539158

That’s a nice start but I cannot see the reasons for the test failures and when I click on "View more details on Check Run Reporter”, I get to the doc page of the tool and I don’t see any other details.

Any idea?

Thanks a lot

@ianwremmel
Copy link
Collaborator

@ianwremmel ianwremmel commented May 30, 2020

hi @vmassol I'm so sorry I missed your issue. A few changes have rolled out in the last few weeks that should make provide a lot more detail.

I click on "View more details on Check Run Reporter”, I get to the doc page

Part of the goal for Check Run Reporter, at least at this stage, is to not need to actually go to Check Run Reporter and, instead, show results on GitHub. Unfortunately, so far as I can tell, I can't get rid of that button :/

@ianwremmel
Copy link
Collaborator

@ianwremmel ianwremmel commented Jun 21, 2020

Closing as it's been three weeks without a response.

@vmassol
Copy link
Author

@vmassol vmassol commented Jun 21, 2020

Thanks for your reply. I had planned to reply to you but first I wanted to test the new version and since I had concluded that GitHub Actions was not ready enough for real usage (since I couldn't fine any working solution to display failed tests and the console execution data), I need to go back to setup all the stuff to try it again (we're currently been using Jenkins for 10+ years and it provides this basic feature of seeing test results from day one). All this to say it's ok to close the issue if you believe it's now provided (that's good). Will take me a while to get back to it.

In case someone is interested, I started doing some comparison at https://dev.xwiki.org/xwiki/bin/view/Community/ContinuousBuild#HCIRequirements

Thanks!

@ianwremmel
Copy link
Collaborator

@ianwremmel ianwremmel commented Jun 21, 2020

Got it, totally understood.

Note that you can use check-run-reporter.com without GitHub Actions. The action is just a light wrapper around the curl command presented at https://www.check-run-reporter.com/repos, so you could run that command in a shell step in Jenkins and still get the annotations on GitHub.

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