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.

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

Trigger test runs periodically to increases failure statistics #5769

merged 1 commit into from
Feb 8, 2022


Copy link

@fjetter fjetter commented Feb 7, 2022

I opted for twice a day since I think this is still doable. The first time slot 6 UTC is US evening and EU early morning.

xref github docs

Note: schedule only applies to default branch

Copy link

github-actions bot commented Feb 7, 2022

Unit Test Results

       16 files   -        1         16 suites   - 1   8h 16m 58s ⏱️ - 47m 47s
  2 595 tests ±       0    2 510 ✔️ ±       0       80 💤 ±  0  5 ±0 
20 462 runs   - 1 366  19 215 ✔️  - 1 291  1 242 💤  - 75  5 ±0 

For more details on these failures, see this check.

Results for commit 8bd64dd. ± Comparison against base commit 9fdada1.

@fjetter fjetter merged commit c830660 into dask:main Feb 8, 2022
@fjetter fjetter linked an issue Feb 8, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

Trigger tests build jobs on main by schedule once a day
1 participant