Skip to content

distributed.tests.test_client.test_nested_compute failing #7483

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

Closed
fjetter opened this issue Jan 17, 2023 · 2 comments · Fixed by #7482
Closed

distributed.tests.test_client.test_nested_compute failing #7483

fjetter opened this issue Jan 17, 2023 · 2 comments · Fixed by #7482
Labels
regression tests Unit tests and/or continuous integration

Comments

@fjetter
Copy link
Member

fjetter commented Jan 17, 2023

https://github.com/dask/distributed/actions/runs/3932865717/jobs/6725937308

distributed.tests.test_client.test_nested_compute seems to pretty consistently fail on win-py3.8

image

I'm surprised this is only happening on windows. I can reproduce this locally as well

2023-01-16 18:13:03,441 - distributed.worker - WARNING - Compute Failed

Key:       fib-10a1838a5b9ea81099d4d0a02946bb70

Function:  fib

args:      (8)

kwargs:    {}

Exception: "RuntimeError('Requested dask.distributed scheduler but no Client active.')"

I suspect this is a regression that was introduced by dask/dask#9808 (although I don't understand how)

@hendrikmakait
Copy link
Member

Re-opened by #7803 which reverts the fix from #7482

@hendrikmakait hendrikmakait reopened this Apr 27, 2023
@fjetter fjetter added tests Unit tests and/or continuous integration regression and removed needs triage labels Dec 12, 2023
@hendrikmakait
Copy link
Member

Looking at the test report, this seems to be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression tests Unit tests and/or continuous integration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants