BASELINE: Update Chromium to 78.0.3904.130

Change-Id: If185e0c0061b3437531c97c9c8c78f239352a68b
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

2 files changed, 46 insertions, 12 deletions

diff --git a/chromium/docs/media/gpu/video_decoder_perf_test_usage.md b/chromium/docs/media/gpu/video_decoder_perf_test_usage.md
index be6b64e0198..26bf41c8537 100644
--- a/chromium/docs/media/gpu/video_decoder_perf_test_usage.md
+++ b/chromium/docs/media/gpu/video_decoder_perf_test_usage.md
@@ -9,8 +9,23 @@ framework.
 [TOC]
 
 ## Running from Tast
-__Note:__ The video decoder performance tests are in the progress of being added
-to the Tast framework. This section will be updated once this is done.
+The Tast framework provides an easy way to run the video decoder performance
+tests from a ChromeOS chroot. Test data is automatically deployed to the device
+being tested. To run all video decoder performance tests use:
+
+    tast run $HOST video.DecodeAccelPerf*
+
+Wildcards can be used to run specific sets of tests:
+* Run all VP8 performance tests: `tast run $HOST video.DecodeAccelPerfVP8*`
+* Run all 1080p 60fps performance tests:
+`tast run $HOST video.DecodeAccelPerf*1080P60FPS`
+
+Check the
+[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/master/src/chromiumos/tast/local/bundles/cros/video/)
+for a list of all available tests.
+See the
+[Tast quickstart guide](https://chromium.googlesource.com/chromiumos/platform/tast/+/HEAD/docs/quickstart.md)
+for more information about the Tast framework.
 
 ## Running manually
 To run the video decoder performance tests manually the
@@ -41,14 +56,30 @@ on the device (e.g. _scaling_governor_, _intel_pstate_). As these can influence
 test results it's advised to disable them.
 
 ## Performance metrics
-Currently uncapped decoder performance is measured by playing the specified test
-video from start to finish. Various performance metrics (e.g. the number of
-frames decoded per second) are collected, and written to a file called
-_perf_metrics/<test_name>.txt_. Individual frame decode times can be found in
-_perf_metrics/<test_name>.frame_times.txt_.
-
-__Note:__ A capped performance test is in the process of being added. This test
-will simulate a more realistic real-time decoding environment.
+To measure decoder performance two different test scenarios are used.
+
+__Uncapped decoder performance:__ In this scenario the specified test video is
+decoded from start to finish as fast as possible. This test scenario provides an
+estimate of the decoder's maximum performance (e.g. the maximum FPS).
+
+__Capped decoder performance:__ This scenario simulates a more realistic
+environment by decoding a video from start to finish at its actual frame rate,
+while simulating real-time rendering. Frames that are not decoded by the time
+they should be rendered will be dropped.
+
+Various performance metrics are collected by these tests:
+* FPS: The average number of frames the decoder was able to decode per second.
+* Frames Dropped: The number of frames that were dropped during playback, only
+relevant for the capped performance test.
+* Dropped frame percentage: The percentage of frames dropped, only relevant for
+the capped performance test.
+* Frame delivery time: The time between subsequent frame deliveries. The average
+frame delivery time and 25/50/75 percentiles are calculated.
+* Frame decode time: The time between scheduling a frame to be decoded and
+getting the decoded frame. This metric provides a measure of the decoder's
+latency. The average decode time and 25/50/75 percentiles are calculated.
+
+All performance metrics are written to _perf_metrics/<test_name>.json_.
 
 ## Command line options
 Multiple command line arguments can be given to the command:
diff --git a/chromium/docs/media/gpu/video_decoder_test_usage.md b/chromium/docs/media/gpu/video_decoder_test_usage.md
index f09c117200e..e86cc82f519 100644
--- a/chromium/docs/media/gpu/video_decoder_test_usage.md
+++ b/chromium/docs/media/gpu/video_decoder_test_usage.md
@@ -15,10 +15,13 @@ framework.
 ## Running from Tast
 The Tast framework provides an easy way to run the video decoder tests from a
 ChromeOS chroot. Test data is automatically deployed to the device being tested.
+To run all video decoder tests use:
 
-    tast run <host> video.<test_name>
+    tast run $HOST video.DecodeAccelH264* video.DecodeAccelVP*
 
-e.g.: `tast run $HOST video.DecodeAccelH264`
+Wildcards can be used to run specific sets of tests:
+* Run all VP8 tests: `tast run $HOST video.DecodeAccelVP8*`
+* Run all VP9 profile 2 tests: `tast run $HOST video.DecodeAccelVP92*`
 
 Check the
 [tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/master/src/chromiumos/tast/local/bundles/cros/video/)