Skip to content

Do not require pytest_timeout for utils_test#6224

Merged
crusaderky merged 1 commit intodask:mainfrom
fjetter:do_not_require_pytest_timeout
Apr 27, 2022
Merged

Do not require pytest_timeout for utils_test#6224
crusaderky merged 1 commit intodask:mainfrom
fjetter:do_not_require_pytest_timeout

Conversation

@fjetter
Copy link
Copy Markdown
Member

@fjetter fjetter commented Apr 27, 2022

Follow up to #6218

downstream users are frequently using utils_test and we should not promote pytest-timeout to a runtime dependency just for that. This replacement captures the gist of the logic although pytest-timeout is dealing with many edge cases. I think we're fine without these edge cases in most situations

@fjetter fjetter changed the title Do not require pytest_timeout Do not require pytest_timeout for utils_test Apr 27, 2022
@fjetter
Copy link
Copy Markdown
Member Author

fjetter commented Apr 27, 2022

@fjetter
Copy link
Copy Markdown
Member Author

fjetter commented Apr 27, 2022

I'm open to vendoring the entire logic, of course. I would just like to avoid having to maintain that list of known debuggers

@github-actions
Copy link
Copy Markdown
Contributor

Unit Test Results

       16 files  +       3         16 suites  +3   7h 26m 53s ⏱️ + 1h 50m 46s
  2 742 tests ±       0    2 659 ✔️ +     11       80 💤  -   13  3 +2 
21 821 runs  +4 239  20 773 ✔️ +4 028  1 045 💤 +209  3 +2 

For more details on these failures, see this check.

Results for commit 36d26f0. ± Comparison against base commit b6a62f8.

@crusaderky
Copy link
Copy Markdown
Collaborator

I agree that vendoring everything is overkill

@crusaderky crusaderky merged commit b837003 into dask:main Apr 27, 2022
@fjetter fjetter deleted the do_not_require_pytest_timeout branch April 28, 2022 16:28
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