Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(213)

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: tools/telemetry/telemetry/web_perf/metrics/rendering_stats.py

Issue 1533523004: Run codespell on src/tools/telemetry. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 5 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« tools/telemetry/telemetry/value/summary.py ('K') | « tools/telemetry/telemetry/web_perf/metrics/blob_timeline_unittest.py ('k') | tools/telemetry/telemetry/web_perf/metrics/timeline_based_metric.py » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: tools/telemetry/telemetry/web_perf/metrics/rendering_stats.py
diff --git a/tools/telemetry/telemetry/web_perf/metrics/rendering_stats.py b/tools/telemetry/telemetry/web_perf/metrics/rendering_stats.py
index 27595da2b8560773da59fd338a01c85ce79c1a6b..65bdbee87c5582f7bd91403b20b81548786d5585 100644
--- a/tools/telemetry/telemetry/web_perf/metrics/rendering_stats.py
+++ b/tools/telemetry/telemetry/web_perf/metrics/rendering_stats.py
@@ -46,7 +46,7 @@ def GetLatencyEvents(process, timeline_range):
Input events dump their LatencyInfo into trace buffer as async trace event
of name starting with "InputLatency". Non-input events with name starting
- with "Latency". The trace event has a memeber 'data' containing its latency
+ with "Latency". The trace event has a member 'data' containing its latency
history.
"""
@@ -68,7 +68,7 @@ def ComputeEventLatencies(input_events):
Input event latency is the time from when the input event is created to
when its resulted page is swap buffered.
- Input event on differnt platforms uses different LatencyInfo component to
+ Input event on different platforms uses different LatencyInfo component to
record its creation timestamp. We go through the following component list
to find the creation timestamp:
1. INPUT_EVENT_LATENCY_ORIGINAL_COMPONENT -- when event is created in OS
« tools/telemetry/telemetry/value/summary.py ('K') | « tools/telemetry/telemetry/web_perf/metrics/blob_timeline_unittest.py ('k') | tools/telemetry/telemetry/web_perf/metrics/timeline_based_metric.py » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698