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

⚠️ CI failed ⚠️ #112

Closed
github-actions bot opened this issue May 8, 2022 · 5 comments
Closed

⚠️ CI failed ⚠️ #112

github-actions bot opened this issue May 8, 2022 · 5 comments
Labels
cause: unknown Root cause could not be identified but issue didn't occur again ci-failure

Comments

@github-actions
Copy link

github-actions bot commented May 8, 2022

Workflow Run URL

@jrbourbeau
Copy link
Member

Looks like there was trouble spinning up Coiled clusters in one of the CI builds with

E           aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host cloud.coiled.io:443 ssl:default [nodename nor servname provided, or not known]

@dchudz @shughes-uk any thoughts?

@ncclementi
Copy link
Contributor

@dchudz Gentle ping. Have you seen this error before?

@dchudz
Copy link
Collaborator

dchudz commented May 16, 2022

I don't think I've seen this. I'm now reading through this (aio-libs/aiohttp#3549), which seems related.

@dchudz
Copy link
Collaborator

dchudz commented May 16, 2022

@ncclementi want to see if this happens again, and ping me if it does? sorry to not have a better answer for now

@jrbourbeau
Copy link
Member

I'll go ahead and close this issue. If it pops up again, a bot will open an issue

@fjetter fjetter added ci-failure cause: unknown Root cause could not be identified but issue didn't occur again labels Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause: unknown Root cause could not be identified but issue didn't occur again ci-failure
Projects
None yet
Development

No branches or pull requests

4 participants