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

Cache test_report shelves in CI #6937

Merged
merged 1 commit into from
Aug 31, 2022
Merged

Conversation

fjetter
Copy link
Member

@fjetter fjetter commented Aug 23, 2022

We're hitting 403 errors which I assume is due to rate limiting. This is not unexpected but we can actually cache the artifacts produced by the script since we're shelving raw XML/json

@fjetter fjetter requested a review from ian-r-rose August 23, 2022 15:51
@fjetter fjetter force-pushed the cache_test_reports branch 2 times, most recently from 1a07409 to 138f04f Compare August 23, 2022 16:01
@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.

       15 files         15 suites   6h 29m 43s ⏱️
  3 041 tests   2 955 ✔️   83 💤 3
22 493 runs  21 516 ✔️ 974 💤 3

For more details on these failures, see this check.

Results for commit 138f04f.

@ian-r-rose
Copy link
Collaborator

@fjetter, I saw a bunch of force pushes to this yesterday (I'm presuming you were doing a workflow dispatch). Is it working to your satisfaction? If so, no objections here.

@fjetter fjetter force-pushed the cache_test_reports branch from 138f04f to 4d4060c Compare August 31, 2022 12:28
@fjetter
Copy link
Member Author

fjetter commented Aug 31, 2022

@fjetter fjetter merged commit a5d6865 into dask:main Aug 31, 2022
@fjetter fjetter deleted the cache_test_reports branch August 31, 2022 12:57
gjoseph92 pushed 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.

2 participants