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.

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

Remove coverage pin from Python 3.10 environment #6439

Merged
merged 1 commit into from
May 25, 2022
Merged

Remove coverage pin from Python 3.10 environment #6439

merged 1 commit into from
May 25, 2022

Conversation

graingert
Copy link
Member

@graingert graingert commented May 25, 2022 •
edited

accidentally left over from #5952 and wasn't reverted via #5717

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

@github-actions
Copy link
Contributor

Unit Test Results

       15 files  ±0         15 suites  ±0   6h 32m 36s ⏱️ + 10m 31s
  2 810 tests ±0    2 727 ✔️  - 3    80 💤 +1  3 ❌ +2 
20 833 runs  ±0  19 902 ✔️  - 2  928 💤 +1  3 ❌ +1 

For more details on these failures, see this check.

Results for commit 0d5b667. ± Comparison against base commit 8035d36.

@jrbourbeau jrbourbeau changed the title remove coverage pin from python 3.10 environment Remove coverage pin from Python 3.10 environment May 25, 2022
jrbourbeau
jrbourbeau approved these changes May 25, 2022
View reviewed changes
Copy link
Member

@jrbourbeau jrbourbeau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @graingert

@jrbourbeau jrbourbeau merged commit 0a77946 into dask:main May 25, 2022
@graingert graingert deleted the remove-coverage-pin branch May 25, 2022 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jrbourbeau jrbourbeau jrbourbeau approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@graingert @jrbourbeau