-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[ci] remove print_test_stats.py #81164
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
Conversation
print_test_stats.py had a somewhat misleading name, as it was also responsible for uploading test statistics to both S3 and Scuba. We are using Rockset for most of this now, so removing the redundant code. The following are things we do *not* have replacements for: - The actual display of regressed or slow tests in the `print_test_stats` job step. I don't think people really looked at these so not a big loss. - Scuba uploads. This is sad, but fundamentally I think we probably don't want to maintain two data pipelines. [ghstack-poisoned]
🔗 Helpful links
❌ 1 New FailuresAs of commit ae990c1 (more details on the Dr. CI page): Expand to see more
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages
|
print_test_stats.py had a somewhat misleading name, as it was also responsible for uploading test statistics to both S3 and Scuba. We are using Rockset for most of this now, so removing the redundant code. The following are things we do *not* have replacements for: - The actual display of regressed or slow tests in the `print_test_stats` job step. I don't think people really looked at these so not a big loss. - Scuba uploads. This is sad, but fundamentally I think we probably don't want to maintain two data pipelines. [ghstack-poisoned]
janeyx99
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A blocker to this is the test_history.py script that the distributed team uses for test case info. Those stats read from S3 to generate a historical view across jobs--maybe an observable view would be sufficient?
cc. @pritamdamania87 (or @pritamdamania?) last time we talked, you were still using this script which was why I didn't merge #73098. Do you still use the script?
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
|
/easycla As part of the transition to the PyTorch Foundation, this project now requires contributions be covered under the new CLA. See #85559 for additional details. This comment will trigger a new check of this PR. If you are already covered, you will simply see a new "EasyCLA" check that passes. If you are not covered, a bot will leave a new comment with a link to sign. |
|
Stack from ghstack (oldest at bottom):
print_test_stats.py had a somewhat misleading name, as it was also
responsible for uploading test statistics to both S3 and Scuba.
We are using Rockset for most of this now, so removing the redundant
code.
The following are things we do not have replacements for:
print_test_statsjob step. I don't think people really looked at theseso not a big loss.
don't want to maintain two data pipelines.