-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
None
-
None
-
None
-
None
-
None
-
None
-
None
One of my patch builds triggered an eslint error that was difficult to diagnose, because none of the failure details appear in the log output for the failed bazel_run_lint task. Only when I ran the lint target locally was I able to see the actual error.