diff options
| author | Klaus Aehlig <klaus.aehlig@huawei.com> | 2022-04-20 17:33:53 +0200 |
|---|---|---|
| committer | Klaus Aehlig <klaus.aehlig@huawei.com> | 2022-04-25 15:46:01 +0200 |
| commit | 4b5dfcecac43e14e57f76993f2431bae5f1866f3 (patch) | |
| tree | 9ec4608fc1dd9023a00a595b41a5c70850441553 /rules/patch | |
| parent | 830380a20f15c6c6d2f91213279c98de9f7cb399 (diff) | |
| download | justbuild-4b5dfcecac43e14e57f76993f2431bae5f1866f3.tar.gz | |
Progress reporting: include origins of running actions
For a user, an important information is to know which actions
are currently running and, more importantly, the target that
caused them. To do so, we need a bit of infrastructure.
- We have to keep track of begin and end of running actions,
as well as the order in which they were started. That has
to happen efficiently and in a thread-safe way.
- We have to compute and keep the origin map for actions,
even if we don't serialize the action graph.
Diffstat (limited to 'rules/patch')
0 files changed, 0 insertions, 0 deletions