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

Enable annotations on failed tests #910

Merged
merged 5 commits into from
Jul 24, 2020
Merged

Enable annotations on failed tests #910

merged 5 commits into from
Jul 24, 2020

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Jul 22, 2020

WIP: Currently waiting for shyim/junit-report-annotations-action#3 fixes.

.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
@webknjaz webknjaz closed this Jul 22, 2020
@webknjaz webknjaz reopened this Jul 22, 2020
.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
.github/workflows/tox.yml Outdated Show resolved Hide resolved
@webknjaz
Copy link
Member

@ssbarnea it works with xunit1 report format: https://github.com/ansible/ansible-lint/pull/910/files#diff-586e1a30597f4eb8296785ca7b4b638eR214. xunit2 doesn't have per-testcase file and per-testsuite is also not implemented in pytest, plus only xunit1 has a line property in the scheme.

.github/workflows/tox.yml Outdated Show resolved Hide resolved
@@ -179,6 +179,11 @@ jobs:
with:
name: logs.zip
path: .tox/**/log/
- name: Report junit failures
uses: shyim/junit-report-annotations-action@master
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure about using master. Should we wait till shyim/junit-report-annotations-action#3 (comment) gets addressed and pin it then?

Copy link
Member Author

Choose a reason for hiding this comment

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

Is ok, the risk is very low. The token is read-only.

Copy link
Member

Choose a reason for hiding this comment

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

My concern is not (only) about that:

  1. The action may suddenly break the interface.
  2. The token only has read-only mode for PR runs, there's still cron runs and tag creations that will run in-repo and have higher privileges.

pytest.ini Outdated Show resolved Hide resolved
ssbarnea and others added 2 commits July 24, 2020 10:30
Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>
@ssbarnea ssbarnea marked this pull request as ready for review July 24, 2020 09:32
@ssbarnea ssbarnea merged commit 4924546 into ansible:master Jul 24, 2020
@ssbarnea ssbarnea deleted the fix/junit branch July 24, 2020 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants