Tonis Tiigi e1da8b7f82 solver: fix printing progress messages after merged edges ...

When different LLB vertexes (eg. parallel requests referencing
local sources from different sessions) generate same cache keys
during solve they are merged together into a single operation.

Currently, when this happened the progress for the vertex that
was dropped got lost. This fixes this case by adding the
progressWriter of the redirected vertex as a target to the
source one.

This should also work with multiple levels of merged edges,
just multiple nested multiwriters as well.

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>

2023-10-23 15:02:53 -07:00

..

controller

progress: use unique id for vertex start/stop

2022-02-24 12:30:41 -08:00

logs

keep buffer of logs to show on failure when regular logs are clipped

2022-01-24 21:30:46 -08:00

progressui

Make output window configurable: BUILDKIT_TTY_LOG_LINES

2023-09-28 13:43:53 -05:00

progresswriter

progressui: adds a json output that shows raw events for the solver status

2023-08-24 16:45:58 -05:00

multireader.go

history api: support for logs of completed builds

2022-12-12 22:15:40 -08:00

multiwriter.go

solver: fix printing progress messages after merged edges

2023-10-23 15:02:53 -07:00

progress_test.go

util/progress: silence go test -race

2023-08-25 10:16:00 -07:00

progress.go

history api: support for logs of completed builds

2022-12-12 22:15:40 -08:00