Bug 210919 - REGRESSION(r260562): [GTK] It caused 3-4 new API tests failures
Summary: REGRESSION(r260562): [GTK] It caused 3-4 new API tests failures
Status: RESOLVED DUPLICATE of bug 210924
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 210854
  Show dependency treegraph
 
Reported: 2020-04-23 10:06 PDT by Carlos Alberto Lopez Perez
Modified: 2020-04-23 10:37 PDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Alberto Lopez Perez 2020-04-23 10:06:53 PDT
It seems r260562 has caused 3-4 new API tests failures.

Check:

GTK-Release-Wayland-Test:
* 260561 Last good run (API tests: ok) https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20Wayland%20%28Tests%29/builds/12038
* 260564 First bad run (API tests: 3 failures) https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20Wayland%20%28Tests%29/builds/12039

GTK-Release-Xvfb-Test
* 260559 Last good run (API tests: ok) https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Tests%29/builds/13449
* 260564 First bad run (API tests: 3 failures) https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Tests%29/builds/13450

So the revision to blame its on the interval [260562-260564]

And looking at  the commits It can only be r260562 since the others 2 in the interval are gardening commits

Also if you look at the red bubble in bug 210854 the EWS already warned there of new failures.
Comment 1 Carlos Alberto Lopez Perez 2020-04-23 10:08:21 PDT
(In reply to Carlos Alberto Lopez Perez from comment #0)
> It seems r260562 has caused 3-4 new API tests failures.

Its actually 3 new failures and 1 new timeout
Comment 2 Carlos Alberto Lopez Perez 2020-04-23 10:37:19 PDT
Patch its going to be rolled out for now.
Marking this as duplicate of bug 210924

*** This bug has been marked as a duplicate of bug 210924 ***