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

Test upcoming Dask 2022.05.2 release #145

Closed
wants to merge 1 commit into from
Closed

Conversation

jrbourbeau
Copy link
Member

@jrbourbeau jrbourbeau commented May 26, 2022

There's a planned dask and distributed release for later today (xref dask/community#250). Let's run CI here against the main branch of dask / distributed to make sure things pass (I expect they will)

@jrbourbeau
Copy link
Member Author

I'm seeing

E           coiled.errors.ServerError: Internal error occured, contact customer service and quote 35214e0e-02a3-4de4-958e-2597ce96b405

in one of the CI builds. cc @dchudz @ntabris @shughes-uk in case you have thoughts

@ntabris
Copy link
Member

ntabris commented May 26, 2022

Internal error occured, contact customer service and quote 35214e0e-02a3-4de4-958e-2597ce96b405

Oddly I can't find this id in our logs. Can you try re-running the CI job and see if it works this time?

@jrbourbeau
Copy link
Member Author

So all the upstream builds are hanging due to dask/distributed#6437. I'll cancel for now and then re-run once dask/distributed#6458 is merged. That PR should fix this issue and also be included in the upcoming release

@jrbourbeau
Copy link
Member Author

jrbourbeau commented May 26, 2022

Okay, so almost all tests are passing now. It looks like one cluster randomly had an issue and failed at client.wait_for_workers(10), which is known to have issues

@jrbourbeau jrbourbeau closed this May 31, 2022
@jrbourbeau jrbourbeau deleted the dask-2022.5.2-test branch May 31, 2022 20:25
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

Successfully merging this pull request may close these issues.

2 participants