Avoid occasional confusion of Flymake C/C++ backend
The regexp would sometimes match non-errors and create a diagnostic with nil severity, which would have consequences for the Flymake engine (these should eventually be addressed, too). * lisp/progmodes/flymake-cc.el (flymake-cc--make-diagnostics): Tighten regexp.
Name | Stage | Failure | ||
---|---|---|---|---|
failed
|
test-all | Test | ||
|