Skip to content

⚠️ CI failed ⚠️ #335

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.

Sign up for GitHub

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

Jump to bottom
Closed
github-actions bot opened this issue Sep 15, 2022 · 3 comments
Closed

⚠️ CI failed ⚠️ #335

github-actions bot opened this issue Sep 15, 2022 · 3 comments
Labels
cause: platform Platform issue (i.e. Coiled specific) cause: upstream (dask) Upstream Dask issue (e.g. API breakage) ci-failure

Comments

@github-actions
Copy link

Workflow Run URL
@ncclementi ncclementi added the cause: upstream (dask) Upstream Dask issue (e.g. API breakage) label Sep 15, 2022
@ncclementi
Copy link
Contributor

Should we skip test_work_stealing_on_scaling_up until is fixed?
cc: @ian-r-rose you mentioned you have seen this one failing before.

@ian-r-rose
Copy link
Contributor

Just opened #336 discussing this -- it's skipped for everything but upstream, but appears to be flaky when it is run.

@fjetter fjetter added the cause: platform Platform issue (i.e. Coiled specific) label Sep 16, 2022
@jrbourbeau
Copy link
Member

Closing in favor of #336

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cause: platform Platform issue (i.e. Coiled specific) cause: upstream (dask) Upstream Dask issue (e.g. API breakage) ci-failure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ian-r-rose @ncclementi @fjetter @jrbourbeau