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

cc-test-reporter throws html: No such file or directory #520

Closed
koic opened this issue Apr 17, 2024 · 3 comments
Closed

cc-test-reporter throws html: No such file or directory #520

koic opened this issue Apr 17, 2024 · 3 comments

Comments

@koic
Copy link

koic commented Apr 17, 2024

I'm not sure of the cause, but I have started to encounter the following error with cc-test-reporter. Since I haven't updated any client libraries, it's likely that something has happened on the server side.

#!/bin/bash -eo pipefail
./tmp/cc-test-reporter before-build
COVERAGE=true bundle exec rake spec
./tmp/cc-test-reporter format-coverage --output tmp/codeclimate.$CIRCLE_JOB.json

./tmp/cc-test-reporter: line 1: html: No such file or directory
./tmp/cc-test-reporter: line 2: syntax error near unexpected token `<'
'/tmp/cc-test-reporter: line 2: `<head><title>504 Gateway Time-out</title></head>

Exited with code exit status 2

https://app.circleci.com/pipelines/github/rubocop/rubocop/11062/workflows/baf07982-a94c-4cc9-98f2-efd26a605f73/jobs/310171

@fede-moya
Copy link
Contributor

Hi @koic!. I'm Fede from CC . Are you constantly experiencing this ? or is something intermittent ?

@koic
Copy link
Author

koic commented Apr 17, 2024

@fede-moya Thank you for the prompt response. Encountered for the first time in rubocop/rubocop#12853. I have not yet reviewed the situation since then.

@koic
Copy link
Author

koic commented Apr 17, 2024

@fede-moya It appears that the cc-test-reporter has recovered in the CI following the merge of the above PR:
https://app.circleci.com/pipelines/github/rubocop/rubocop/11063/workflows/2277e517-4e23-46d3-a18a-d2a86aa9c03a/jobs/310195

It may have been a temporary encounter with "504 Gateway Time-out" issue. For now, I will close this issue. I will reopen it if the problem recurs. Thank you for taking your time.

@koic koic closed this as completed Apr 17, 2024
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