[Webkit-unassigned] [Bug 244621] New: GCC does not have an error maximum, breaking EWS on bad patches

[bugzilla-daemon at webkit.org]

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

            Bug ID: 244621
           Summary: GCC does not have an error maximum, breaking EWS on
                    bad patches
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: emw at apple.com

For example: https://github.com/WebKit/WebKit/commit/fdc83ec3c441df44f9e272d1426baa01fdb287fe introduced errors in the WPE build, and caused https://ews-build.webkit.org/#/builders/8/builds/96909 to spend > 5 hrs compiling, generating millions of lines of output. 99% of those lines were error output, and there were 100k errors emitted in total.

Clang avoids explosive situations like this by bailing out after 20 errors (configurable by the -ferror-limit=<n> option). GCC doesn't have an error limit by default, but one can be configured using -fmax-errors=<n>. We should use this to match GCC's behavior to clang's.

-- 
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/20220831/0da75c99/attachment.htm>