Support absolute timestamp of torch profiler before 2.4 #541
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #541 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 19 19
Lines 2132 2132
=========================================
Hits 2132 2132 ☔ View full report in Codecov by Sentry. |
gaogaotiantian
force-pushed
the
optional-basetime
branch
from
96697ae to
1ebde69
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Starting pytorch 2.4.0 (I think), they used a basetime offset + relative timestamp for trace events. Before that (at least for 2.3.0 I tested) they were using absolute timestamp. This PR makes both schema supported.