diff options
| author | Scott Wittenburg <scott.wittenburg@kitware.com> | 2022-11-03 13:33:52 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-03 13:33:52 -0600 |
| commit | b55509ffa89f847df3c24ff2a90ce8a11d154a96 (patch) | |
| tree | b8e1dcaff2a966eb98077998d6978e899eacc649 /var | |
| parent | 08bee718a26c96ceffd228e4917358570239ede1 (diff) | |
| download | spack-b55509ffa89f847df3c24ff2a90ce8a11d154a96.tar.gz spack-b55509ffa89f847df3c24ff2a90ce8a11d154a96.tar.bz2 spack-b55509ffa89f847df3c24ff2a90ce8a11d154a96.tar.xz spack-b55509ffa89f847df3c24ff2a90ce8a11d154a96.zip | |
gitlab: Prune untouched specs less aggressively (#33669)
Untouched spec pruning was added to reduce the number of specs
developers see getting rebuilt in their PR pipelines that they
don't understand. Because the state of the develop mirror lags
quite far behind the tip of the develop branch, PRs often find
they need to rebuild things untouched by their PR.
Untouched spec pruning was previously implemented by finding all
specs in the environment with names of packages touched by the PR,
traversing in both directions the DAGS of those specs, and adding
all dependencies as well as dependents to a list of concrete specs
that should not be considered for pruning.
We found that this heuristic results in too many pruned specs, and
that dependents of touched specs must have all their dependencies
added to the list of specs that should not be considered for pruning.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions