-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Unable to generate test report #118
Comments
This is a limitation of the GitHub API. The excess text will be truncated, but a test report should be generated. Are you running tests triggered by Pull Requests? If the Pull Request doesn't exist, then it may not have Checks. Anyway, more information is needed. |
The description of the issue is a big vague, so I'm not sure if I'm having the same issue... However: my summary is less than 65k, doesn't get truncated. But the test report isn't generated. Here's the branch I'm working on (sorry for the mess with the hundreds of commits, I'm still learning to use GitHub actions). In particular: - name: Test
run: |
xcodebuild -workspace SlimHUD.xcworkspace -scheme SlimHUD -destination platform=macOS -resultBundlePath TestResults test
- name: Public test results
uses: kishikawakatsumi/[email protected]
if: always()
with:
path: "TestResults.xcresult"
title: Coverage results
upload-bundles: never
show-code-coverage: true However, as you can also see here, there are only two checks. The one with the title At some point I managed to get it being created, see here. The workflow file used in this run consistently worked. Changing even just one line, in other steps of the workflow, made it fail. Interestedly enough, this workflow now has two generated reports, one of them created an hour after the job had been run. Looking at the source code of xcresulttool I'd expect the check with the output to be created, as soon as its step has been finished. In fact, with the workflow files that managed to create the report, it was available immediately (actually, before its completion, as soon as its step had finished). Do you have any idea what could be causing this? Edit / SolutionIn my case the error was in the |
For above getting Annotation Errors
The text was updated successfully, but these errors were encountered: