-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
Test report publishing fails following v3.3.0 release #637
Comments
@bogdanbranisteanu thank you for the report. Are you using the specific version Could be related to: https://github.com/mikepenz/action-junit-report/blob/main/src/annotator.ts#L140-L143 Is this on an open source repo? E.g. GitHub Cloud or enterprise server? |
Tried with both @v3.3.0 and @V3 and it was failing. Now changed to @v3.2.0 and it works just fine. The projects are on an enterprise server. |
Wonder if it may be due to the upgrade to |
I've recompiled Would you please be so kind to test if that is the cause of the problem.
(generally speaking commit hash pinning is from a security perspective advised - https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions) |
It's still failing. |
@bogdanbranisteanu thank you for trying this variant. What seems strange, it should fail also on v3.2.0 given that it also posts a job summary. I am sorry that I have to rely on you testing this - Really appreciate your help. Prepared a new commit which allows to disable the publishing of the job summary at the end:
|
This one works fine. |
Published v3.3.1 which offers the APi to disable |
I can confirm that all projects can now successfully publish the test reports. Thanks a lot for the cooperation and quick fix! |
Hi, I have been using your test report publishing scripts in several projects. Today you released a new version and since then the publishing fails.
It seems to have something to do with the summary input, but this input is described as optional in the documentation.
The text was updated successfully, but these errors were encountered: