Skip to content

Conversation

@gjoseph92
Copy link
Collaborator

These tests were identical, and redundant with tests we already have. The "fast" aspect doesn't make sense to test in CI; restarting processes can actually be very, very slow on some CI workers.

Closes #6746

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

These tests were identical, and redundant with tests we already have. The "fast" aspect doesn't make sense to test in CI, restarting processes can actually be very, very slow on some CI workers.
@gjoseph92 gjoseph92 requested a review from hendrikmakait July 20, 2022 19:16
@github-actions
Copy link
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

       14 files   -        1         14 suites   - 1   6h 14m 56s ⏱️ - 24m 21s
  2 977 tests  -        3    2 887 ✔️  -        3    88 💤 ±    0  2 ±0 
20 869 runs   - 1 807  19 888 ✔️  - 1 671  979 💤  - 136  2 ±0 

For more details on these failures, see this check.

Results for commit 1cf4d83. ± Comparison against base commit f30bacc.

@gjoseph92
Copy link
Collaborator Author

@gjoseph92 gjoseph92 merged commit add3663 into dask:main Jul 21, 2022
@gjoseph92 gjoseph92 deleted the test_restart_fast_sync branch July 21, 2022 14:38
gjoseph92 added a commit to gjoseph92/distributed that referenced this pull request Oct 31, 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.

Flaky test_restart_fast_sync and test_fast_kill

2 participants