hack/select-e2e.sh escalated to the full Chainsaw suite when a changed
packages/* component resolved into the PackageSource graph but had no
*-application descendant, via the empty-final_apps safety net. That net
keyed off the combined selection, so a PR that also touched one unrelated
suite's tests contributed that suite through selected_apps and made
final_apps non-empty, silently swallowing the escalation: the same
system-package change selected the full suite alone but exactly one suite
alongside a suite edit.
Decide the escalation from the source-derived selection alone
(sources_apps) instead of the combined result, then union the directly
selected per-suite edits afterwards. Keep the original empty-final_apps
catch-all for a per-suite edit on a directory with no chainsaw-test.yaml.
Add a regression test covering a no-app-descendant package change combined
with an unrelated per-suite edit.
Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
IvanHunters
c0a563af48