Skip to content

Failing workflows should print at least one error from the failures #11

@joestringer

Description

@joestringer

In a recent example failure of a workflow, the tail end of the log just prints "false" many times, each time on a new line. This makes it hard to understand what was causing the problem.

If you download the artifacts for the failure, the *_response.json files contain the failure case. The workflow should print at least one of these failures in the CI log to make it easier to understand what went wrong during the scraping operation.

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