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

Workflow failing #211

Closed
richardlau opened this issue Feb 24, 2022 · 3 comments · Fixed by #212
Closed

Workflow failing #211

richardlau opened this issue Feb 24, 2022 · 3 comments · Fixed by #212

Comments

@richardlau
Copy link
Member

The last two actions workflow runs have failed so we've stopped getting the daily reports

/home/runner/work/_temp/97f51af9-1853-4022-8d18-6741de989026.sh: line 3: /usr/bin/curl: Argument list too long
Error: Process completed with exit code 126.
richardlau added a commit that referenced this issue Feb 25, 2022
Pass POST data to curl via a file to avoid getting an
`Argument list too long` error.

Fixes: #211
richardlau added a commit that referenced this issue Feb 27, 2022
Pass POST data to curl via a file to avoid getting an
`Argument list too long` error.

Fixes: #211
@richardlau
Copy link
Member Author

It looks like we now have a different failure -- node-core-utils running out of memory, most probably due to the high number of test failures (3600(!) per run) in https://ci.nodejs.org/job/node-test-pull-request/42798/:
https://github.com/nodejs/reliability/runs/5347224082?check_suite_focus=true

@richardlau richardlau reopened this Feb 27, 2022
@richardlau
Copy link
Member Author

We've had a couple of runs that are marked green, but they haven't created the issue summaries:

image

e.g. https://github.com/nodejs/reliability/runs/5415619624?check_suite_focus=true

Run title_date=$(date +%Y-%m-%d)
  title_date=$(date +%Y-%m-%d)
  echo "{ \"title\": \"CI Reliability ${title_date}\", \"body\": " >> body.json
  cat results.md | python -c 'import json,sys; print(json.dumps(sys.stdin.read()))' >> body.json
  echo "}" >> body.json
  curl --request POST \
  --url https://api.github.com/repos/${GITHUB_REPOSITORY}/issues \
  --header 'authorization: ***' \
  --header 'content-type: application/json' \
  --data @body.json
  shell: /usr/bin/bash -e {0}
  % 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  [2](https://github.com/nodejs/reliability/runs/5415619624?check_suite_focus=true#step:8:2)80k  100   419  100  279k   205[3](https://github.com/nodejs/reliability/runs/5415619624?check_suite_focus=true#step:8:3)  1372k --:--:-- --:--:-- --:--:-- 137[4](https://github.com/nodejs/reliability/runs/5415619624?check_suite_focus=true#step:8:4)k
{
  "message": "Validation Failed",
  "errors": [
    {
      "resource": "Issue",
      "code": "custom",
      "field": "body",
      "message": "body is too long"
    },
    {
      "resource": "Issue",
      "code": "custom",
      "field": "body",
      "message": "body is too long (maximum is 6[5](https://github.com/nodejs/reliability/runs/5415619624?check_suite_focus=true#step:8:5)53[6](https://github.com/nodejs/reliability/runs/5415619624?check_suite_focus=true#step:8:6) characters)"
    }
  ],
  "documentation_url": "https://docs.github.com/rest/reference/issues#create-an-issue"
}

@richardlau
Copy link
Member Author

We got a report today 🎉 #214
The problematic build which had a large number of failures must have finally been pushed out of range of the most recent builds being looked at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant