Bug 195134 – [GTK] New CPU profiler tests failing

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKitGTK

[Alicia Boya García]

inspector/cpu-profiler/threads.html
inspector/cpu-profiler/tracking.html

Introduced in r241739.

--- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/inspector/cpu-profiler/threads-expected.txt
+++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/inspector/cpu-profiler/threads-actual.txt
@@ -10,13 +10,10 @@
 PASS: Event should have a timestamp.
 PASS: Event should have a usage.
 PASS: usage should be greater than or equal to zero.
-PASS: Event should have threads.
-PASS: Every thread has between 0 and 100 usage.
-PASS: Event should have 1 main thread.
-PASS: Event should have 2 worker threads.
-PASS: Event should have other worker threads.
-PASS: Worker 1 usage should be greater than zero.
-PASS: Worker 2 usage should be greater than zero.
-PASS: Total usage should be greater than or equal to the sum of both worker threads.
-CPUProfiler.trackingComplete
+FAIL: Event should have threads.
+    Expected: truthy
+    Actual: false
+!! EXCEPTION: undefined is not an object (evaluating 'messageObject.params.event.threads')
+Stack Trace: #0: (anonymous) (unknown)
+#1: promiseReactionJob [native code]

[Miguel Gomez]

inspector/cpu-profiler/tracking.html is passing since r244478.

[Diego Pino]

Created attachment 410627 [details]
Patch

[Diego Pino]

inspector/cpu-profiler/threads.html is a flaky failure. It has been passing since r266388, but it fails occasionally. For instance:

Diff: https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r267958%20(16233)/inspector/cpu-profiler/threads-diff.txt

--- /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/inspector/cpu-profiler/threads-expected.txt
+++ /home/buildbot/worker/gtk-linux-64-release-tests/build/layout-test-results/inspector/cpu-profiler/threads-actual.txt
@@ -17,6 +17,8 @@
 PASS: Event should have other worker threads.
 PASS: Worker 1 usage should be greater than zero.
 PASS: Worker 2 usage should be greater than zero.
-PASS: Total usage should be greater than or equal to the sum of both worker threads.
+FAIL: Total usage should be greater than or equal to the sum of both worker threads.
+    Expected: greater than or equal to 198.53888702392578
+    Actual: 198.53887939453125
 CPUProfiler.trackingComplete

The difference is minimal. I pushed a patch to round the decimal part to 4 digits only.

[Joseph Pecoraro]

Comment on attachment 410627 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=410627&action=review

> LayoutTests/inspector/cpu-profiler/threads.html:52
> +                let totalUsage = Float(messageObject.params.event.usage.toFixed(4));

Err, no such thing as `Float()` in JavaScript?

> ! EXCEPTION: Can't find variable: Float
>  21Stack Trace: #0: (anonymous) (unknown)
>  22#1: promiseReactionJob [native code]

Would this work?

    let totalUsage = messageObject.params.event.usage.toFixed(4);
    let workersUsage = (workers[0].usage + workers[1].usage).toFixed(4);

[Diego Pino]

Created attachment 410736 [details]
Patch

[EWS]

Committed r268174: <https://trac.webkit.org/changeset/268174>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 410736 [details].