Fix immediate profiler step range boundary (#30215)
Co-authored-by: weireweire <20922698+weireweire@users.noreply.github.com>
This commit is contained in:
@@ -144,7 +144,7 @@ class SchedulerProfilerManager:
|
|||||||
self.profiler_start_forward_ct + num_steps
|
self.profiler_start_forward_ct + num_steps
|
||||||
)
|
)
|
||||||
else:
|
else:
|
||||||
self.profiler_target_forward_ct = self.get_forward_ct() + num_steps
|
self.profiler_target_forward_ct = self.get_forward_ct() + num_steps + 1
|
||||||
# The caller will be notified when reaching profiler_target_forward_ct
|
# The caller will be notified when reaching profiler_target_forward_ct
|
||||||
else:
|
else:
|
||||||
self.profiler_target_forward_ct = None
|
self.profiler_target_forward_ct = None
|
||||||
|
|||||||
Reference in New Issue
Block a user