Closed Trott closed 3 years ago
The job, e.g. https://ci.nodejs.org/view/Node.js%20Daily/job/node-test-commit-linux-coverage-daily/869/nodes=benchmark/console is unable to ssh into the coveragedata
host:
04:12:31 + rsync -r out coveragedata:coverage-out
04:12:31 ssh_exchange_identification: read: Connection reset by peer
04:12:39 rsync: connection unexpectedly closed (0 bytes received so far) [sender]
04:12:39 rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1]
I can't either :disappointed:
I've tried rebooting from the softlayer console. Now I just get:
ssh: connect to host 50.97.245.4 port 22: Connection refused
I'm wondering if it might be related to what happened to the release ci.
ok seems to have come back now and I can ssh in. Hopefully next coverage run will work.
Having said that @richardlau it might have failed because a cleanup is needed.
Right, but without being able to ssh in I couldn't cleanup. I'll take a look now.
I've run a cleanup. I've also started a run of the coverage job: https://ci.nodejs.org/view/Node.js%20Daily/job/node-test-commit-linux-coverage-daily/871/
hmm I guess I was also supposed to clean up on the test machine as well as the benchmark data machine.
Cleaned up on both the test machine and benchmark data machine. Trying again: https://ci.nodejs.org/view/Node.js%20Daily/job/node-test-commit-linux-coverage-daily/872/
Cleanup done on both the test and benchmark machine and the job passed. We have coverage on https://coverage.nodejs.org/ with click through data for the last 15 days (the cleanup involves deleting older directories).
Seems like this can be closed, but re-open if I'm mistaken of course.
I mentioned this in the Slack on Friday but probably should have opened an issue instead. coverage.nodejs.org hasn't reported anything since April 10.