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

The github action failed to post reports #355

Open
joyeecheung opened this issue Aug 24, 2022 · 5 comments
Open

The github action failed to post reports #355

joyeecheung opened this issue Aug 24, 2022 · 5 comments

Comments

@joyeecheung
Copy link
Member

joyeecheung commented Aug 24, 2022

From a recent run:

Run title_date=$(date +%Y-%m-%d)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 69480  100   296  100 69184    736   168k --:--:-- --:--:-- --:--:--  168k
{
  "message": "Validation Failed",
  "errors": [
    {
      "resource": "Issue",
      "code": "custom",
      "field": "body",
      "message": "body is too long (maximum is 65536 characters)"
    }
  ],
  "documentation_url": "https://docs.github.com/rest/reference/issues#create-an-issue"
}
100 69480  100   296  100 69184    736   168k --:--:-- --:--:-- --:--:--  168k

I am guessing that the recent debugger tests fallouts resulted in a super long report that couldn't be posted in one go due to rescritions of GitHub. We probably need to update the action so that it split different parts into replies in that case.

@joyeecheung
Copy link
Member Author

Another thing it could do is to commit that report into this repository, and post a link to that document.

@joyeecheung
Copy link
Member Author

Looks like the report is short enough to be posted again: #356

But it may be good to always create a file in this repo anyway, for posterity. I found the doc on how to create the file using the RESTful API:https://docs.github.com/en/rest/repos/contents#create-or-update-file-contents

@richardlau
Copy link
Member

I have a PR that pastes the generated markdown into GitHub Actions step summary for the job: #274
I don't know if the step summaries have similar size limits. I also suspect they won't persist as action logs eventually get purged.

@joyeecheung
Copy link
Member Author

Indeed, it seems the summary from https://github.com/nodejs/reliability/actions/runs/2314866636 is already unavailable.

@joyeecheung
Copy link
Member Author

joyeecheung commented Aug 24, 2022

I think for summaries we could also just post the stats (i.e. cut everything up to the ### Jenkins Failure section), and maybe include the progress (i.e. everything after ### progress), that would look more like an actual summary of things

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

2 participants