We attempted to do this by trying to adjust build runvars only if they didn't have a `.'. But cs-adjust-flight runvar-build-set has special handling for <old-value>: it is always qualified with the flight.
So change the match to look for the current flight number. Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com> --- mg-repro-setup | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mg-repro-setup b/mg-repro-setup index 0b3137a..4f2fe54 100755 --- a/mg-repro-setup +++ b/mg-repro-setup @@ -199,7 +199,7 @@ if $skipcapture; then adjrunvar skip_testids "capture-logs*"; fi ./cs-adjust-flight $flight \ copy-jobs $example_flight $job \ - runvar-build-set . '/buildjob$' '^[^\.]+$' $example_flight \ + runvar-build-set . '/buildjob$' "^$flight\\." $example_flight \ "${adjusts[@]}" progress "executing ..." -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel