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

Support GitHub Actions output #368

Open
paulz opened this issue Jun 20, 2020 · 2 comments
Open

Support GitHub Actions output #368

paulz opened this issue Jun 20, 2020 · 2 comments

Comments

@paulz
Copy link

paulz commented Jun 20, 2020

It would nice to have xcpretty formatter that supports GitHub Actions warnings and errors.

Similar to travis formatter: https://github.com/kattrali/xcpretty-travis-formatter

Currently when xcodebuild fails on GitHub action with xcpretty default formatter we get:

Annotations

 Check failure on line 1 in .github

 @github-actions
github-actions
/ build-and-test

.github#L1
Xcodebuild action failed (65)!
 Check failure on line 1 in .github

 @github-actions
github-actions
/ build-and-test

.github#L1
Xcodebuild action failed (65)!

which incorrectly reports failures on line 1 of the workflow file.

See example:
https://github.com/sparta-science/MacSwitchActivation/actions/runs/141734946

It would be very helpful to see failure file and line number, such as

UITests.swift:54

https://github.com/sparta-science/MacSwitchActivation/runs/790560979?check_suite_focus=true#step:4:38

GitHub Actions support setting errors and warnings:
https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-error-message

@samshiffman321
Copy link

I'm also having issues with xcpretty and github actions, I'm getting test failures but the pipeline still passes. is this going to be fixed any time soon?

@Justintime50
Copy link

@samshiffman321 I think what you are reporting is slightly different than what the author of this issue is asking about. I've filed another issue for what you are seeing as I too have the same problem: #386

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

3 participants