Skip to content

Huge console output causes 400 errors #6

@l-abels

Description

@l-abels

I have a few Jest tests that produce a lot of console output. The tests pass, but the annotation never updates and the following error is produced:



jest-buildkite-reporter failed on endpoint 'https://agent.buildkite.com/v3' and job '[build id]':
 VError: POST request to Buildkite at 'https://agent.buildkite.com/v3/jobs/[build id]/annotations' failed: Request failed with 400: Bad Request

I'm making the assumption that the size of the console output is to blame here. If this is the case, should we limit console output to some finite size?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions