Skip to content

Execution failed: stdout maxBuffer length exceeded on GitHub Actions (Windows Server 2025) #128

@muzanella11

Description

@muzanella11

Description:

When running a workflow on GitHub Actions with the Windows Server 2025 runner, the build process fails with the following error:
Image

Steps to Reproduce:

  1. Use the windows-2025 runner in a GitHub Actions workflow.
  2. Run a build/compile job (e.g., npm run build or another command).
  3. The process produces a large amount of output logs.
  4. The job fails with stdout maxBuffer length exceeded.

Expected Behavior:

The workflow should complete successfully even if the build produces a large amount of log output.

Actual Behavior:

The build stops with stdout maxBuffer length exceeded before completing.

Possible Solutions (Optional):

  • If using child_process.exec, increase the maxBuffer option.
  • Consider switching to spawn to handle logs as a stream instead of a buffer.
  • Reduce verbosity of log output to avoid hitting the buffer limit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions