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

No report available #167

Open
mastoj opened this issue Apr 7, 2022 · 7 comments
Open

No report available #167

mastoj opened this issue Apr 7, 2022 · 7 comments

Comments

@mastoj
Copy link

mastoj commented Apr 7, 2022

I have a strange issue that surface that last couple of days.

Everything seems to be ok, and I can see that the report has been generated and have a "Check run HTML" url in my action output. When I click that url I get a 404, and the report isn't available in the sidebar menu either.

Is this something that more people has experienced? Is it because a branch might have been deleted or why might this be?

@katerynamaruk
Copy link

I have faced with the similar issue. After Workflow run no Report was generated. Although no errors are exist in Report generating process.
maven_report

@mwagenma-maersk
Copy link

You could check whether multiple workflows were triggered by the same event. This might be a similar issue as EnricoMi/publish-unit-test-result-action#12 where the test results are appended to another workflow run.

@ralfstuckert
Copy link

My observations by now:

  • If a worfklow was triggered by a commit, the report appears.
  • If a report was triggered by a workflow_dispatch, the report does not appear. Check run URL gives a 404. Check run HTML links to the report of the last worklfow triggered by a commit.

And by the way: this does not happen with the EnricoMi/publish-unit-test-result-action, so this seems to be a different problem

@serard-bimandco
Copy link

Get the same problem.

Any update on this ? 👍

@gerardkmiec
Copy link

got the same issue, but it looks like no update was made for over a year...

@esumerfd
Copy link

esumerfd commented Feb 6, 2024

Same issue here. Can't see why the GHA workflow laungh type would affect this step.

@MattWalker414
Copy link

Seeing the same issue. Has anyone gotten around this issue.

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

8 participants