add xpu_timer:train.py #1621
Open
add xpu_timer:train.py #1621
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
samplise
requested review from
BalaBalaYi,
nash635 and
workingloong
as code owners
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## xpu_timer_experiments #1621 +/- ##
======================================================
Coverage 84.29% 84.30%
======================================================
Files 285 285
Lines 30292 30292
======================================================
+ Hits 25536 25538 +2
+ Misses 4756 4754 -2 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Please describe the changes you have made or proposed in this pull request.
Why are the changes needed?
Explain the purpose or motivation behind these changes. What problem are you trying to solve?
Does this PR introduce any user-facing change?
Specify whether this pull request introduces any changes that users will directly interact with or notice.
How was this patch tested?
Detail the testing process you have undertaken to ensure the changes in this pull request are valid and working as intended.