Re: How to do add-on merge requests and get a pipeline to run?

On 2026-08-18 00:33, David Kastrup wrote:
> Dan Eble <[email protected]> writes:
...
>> We need to run the regression-test difference detector.  A merge
>> request should not be labeled Patch::review until someone has recorded
>> the test differences in the comments.
> 
> Ok.  I'll have to think about how to get there with reasonable effort.

Two alternatives come to mind:

1. Run tests on the top of the stack only, relative to master; refer 
reviewers of underlying MRs to the top-of-stack results.  I don't know 
if the workflow definition can tell whether an MR is currently on top, 
and even if it can, another MR could later be added to the stack.  Maybe 
this is feasible and maybe it isn't.

2. Run on each MR relative to its immediate base.  Speaking for myself 
only, as someone who has a runner in the pool, I wouldn't mind if we 
scripted the checking job so that in a stacked MR, it took time to 
measure the baseline itself instead of downloading an archive of 
prebuilt results.  I'm biased toward donating processing time more than 
network I/O; others might be in a different situation.
-- 
Dan