Add a consistent check API step so we can track our usage #77998
Conversation
🔗 Helpful links
✅ No Failures (25 Pending)As of commit a472dae8b0 (more details on the Dr. CI page): Expand to see more💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
janeyx99
force-pushed
the
add-check-api-rate
branch
from
a472dae to
05f9fd3
Compare
|
@pytorchbot merge -f |
|
Hey @janeyx99. |
…77998) Summary: Followup action to our API Limit SEV: #77194 I added this to the upload-test-stats workflow because that one has repo secret access and is run regularly enough to be able to capture the API usage situation. The next step in the future will be to log our usage to Rockset so we can see a trend + better preempt this. Pull Request resolved: #77998 Approved by: https://github.com/malfet Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/1b878b4eaa984b7b1929a7d077078481d1d87e94 Reviewed By: seemethere Differential Revision: D36599566 Pulled By: seemethere fbshipit-source-id: 36cfffc30ddb3248818c88bc9ccdfbcf553af7c6
Followup action to our API Limit SEV: #77194 I added this to the upload-test-stats workflow because that one has repo secret access and is run regularly enough to be able to capture the API usage situation. The next step in the future will be to log our usage to Rockset so we can see a trend + better preempt this. Pull Request resolved: #77998 Approved by: https://github.com/malfet
4 participants
Followup action to our API Limit SEV: #77194
I added this to the upload-test-stats workflow because that one has repo secret access and is run regularly enough to be able to capture the API usage situation.
The next step in the future will be to log our usage to Rockset so we can see a trend + better preempt this.