[Webkit-unassigned] [Bug 229533] New: [EWS] compile-webkit-without-patch failed, but bot ran layout tests anyway and blamed the patch for a pre-existing failure

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=229533

            Bug ID: 229533
           Summary: [EWS] compile-webkit-without-patch failed, but bot ran
                    layout tests anyway and blamed the patch for a
                    pre-existing failure
           Product: WebKit
           Version: Other
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ryanhaddad at apple.com

As you can see in https://ews-build.webkit.org/#/builders/60/builds/10553, the layout-tests and re-run-layout-tests both failed. The bot then proceeded to the compile-webkit-without-patch step and failed to compile. 

Surprisingly, the bot still proceeded to the run-layout-tests-without-patch step, which failed with the following:

16:30:10.005 10889 WebKitTestRunner was not found at /Volumes/Data/worker/macOS-AppleSilicon-Big-Sur-Debug-WK2-Tests-EWS/build/WebKitBuild/Debug/WebKitTestRunner

I would expect that the EWS run would be considered inconclusive or invalid, but instead it blamed the patch under test for introducing a new test failure that really should have been considered pre-existing.

Other examples from around the same time:
https://ews-build.webkit.org/#/builders/60/builds/10560
https://ews-build.webkit.org/#/builders/60/builds/10561
https://ews-build.webkit.org/#/builders/60/builds/10562
https://ews-build.webkit.org/#/builders/60/builds/10563

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210826/b1eb07ec/attachment-0001.htm>