Skip to content

Fix fail_hard for sync functions #6269

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

Merged
merged 1 commit into from
May 13, 2022
Merged

Conversation

gjoseph92
Copy link
Collaborator

The else meant we would, in fact, not fail hard at all.

cc @fjetter @mrocklin xref #6210

  • Tests added / passed
  • Passes pre-commit run --all-files

The `else` meant we would, in fact, not fail hard at all.
@github-actions
Copy link
Contributor

github-actions bot commented May 4, 2022

Unit Test Results

       16 files  ±0         16 suites  ±0   7h 38m 31s ⏱️ - 29m 15s
  2 746 tests ±0    2 662 ✔️  - 1       81 💤 ±0  3 +1 
21 864 runs  ±0  20 812 ✔️  - 1  1 047 💤 ±0  5 +1 

For more details on these failures, see this check.

Results for commit 122df57. ± Comparison against base commit baf05c0.

@mrocklin
Copy link
Member

mrocklin commented May 4, 2022

Yup. That looks dumb. I'm surprised that this didn't kill things ?

@mrocklin mrocklin merged commit 4b34bd4 into dask:main May 13, 2022
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