Skip to content

Change log levels for common errors

Steve Xuereb requested to merge 4699-high-volume-of-sentry-errors into master

What does this MR do?

Change log levels for common errors

Why was this MR needed?

As shown in #4699 (closed) we get a ton of "errors" which are not really actionable but are important to know about when debugging a real problem.

The Failed to process runner is very common because it's also returned when a Job fails.

Problem while reading command output is also common when the docker machine file doesn't exist anymore.

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

Closes #4699 (closed)

Edited by Steve Xuereb

Merge request reports