Bug 153942

Summary: [GTK] Private browsing mode tests are flaky
Product: WebKit Reporter: Michael Catanzaro <mcatanzaro>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: bugs-noreply, cgarcia
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   

Michael Catanzaro
Reported 2016-02-06 09:15:46 PST
plugins/private-browsing-mode-2.html and plugins/private-browsing-mode.html have been flaky since r191881, around when we landed several RunLoop/WorkQueue/GMainLoopSource changes: --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/plugins/private-browsing-mode-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/plugins/private-browsing-mode-actual.txt @@ -5,8 +5,8 @@ PASS plugin1.privateBrowsingEnabled is false PASS plugin1.cachedPrivateBrowsingEnabled is false -PASS plugin1.privateBrowsingEnabled is true -PASS plugin1.cachedPrivateBrowsingEnabled is true +FAIL plugin1.privateBrowsingEnabled should be true. Was false. +FAIL plugin1.cachedPrivateBrowsingEnabled should be true. Was false. PASS plugin2.privateBrowsingEnabled is true PASS plugin2.cachedPrivateBrowsingEnabled is true --- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/plugins/private-browsing-mode-2-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/plugins/private-browsing-mode-2-actual.txt @@ -4,8 +4,8 @@ PASS plugin1.privateBrowsingEnabled is false -PASS plugin1.privateBrowsingEnabled is true +FAIL plugin1.privateBrowsingEnabled should be true. Was false. PASS plugin2.privateBrowsingEnabled is true PASS plugin1.privateBrowsingEnabled is false -PASS plugin2.privateBrowsingEnabled is false +FAIL plugin2.privateBrowsingEnabled should be false. Was true. https://build.webkit.org/results/GTK Linux 64-bit Release (Tests)/r196216 (13627)/results.html#
Attachments
Add attachment proposed patch, testcase, etc.
Carlos Garcia Campos
Comment 1 2020-08-17 06:35:03 PDT
Plugins are no longer supported.
Note You need to log in before you can comment on or make changes to this bug.