Skip to content

Add more context when workflow_job event isn't accepted due to label mismatch #4760

@yangmillstheory

Description

@yangmillstheory

We spent quite a bit of time at work today trying to debug why a job wasn't picked up. The root cause was basically that the label was ['a, b, c', d, e] when it should have been [a, b, c, d, e].

Looking at the Lambda logs, we currently only log the not matching label

logger.warn(`Received event contains runner labels '${body.workflow_job.labels}' that are not accepted.`);

but not any further context. Logging the context would have helped quite us root-cause the issue quite faster.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions