microsoft / microsoft/just

Parallel Webpack builds fail to report errors

Open
#550 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2k
Forks
97
PR merge metrics
No merged PRs in 30d

Description

We've seen this primarily in Azure DevOps linux pipeline agents (doesn't seem to repro on windows), where we have a just task with multiple parallel webpack builds and sometimes there won't be outputs for some of the webpack builds, nor errors. Our just config has something along the lines of this:

series( parallel( webpackCliTask(...), webpackCliTask(...), webpackCliTask(...), webpackCliTask(...), webpackCliTask(...), webpackCliTask(...)), 'postWebpackTask');

The postWebpackTask will still execute in cases where not all of the webpack bundles are observed. Haven't been able to nail down a firm root cause (e.g. is the webpack process dead? do we fail to wait for all of them correctly?)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the just configuration using parallel webpackCliTask calls followed by series and postWebpackTask on a Linux agent. Observe whether webpack processes exit, whether all outputs appear, and when errors are reported. Done means parallel builds reliably report failures or wait for every expected bundle before postWebpackTask runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, webpack
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.