I just got tripped up again by putting a build job filter definition
after the call to create_build_jobs. Reorder the make-*flight scripts
to reduce the probability of me doing so any more times.
The general order of these scripts is now:
- job filter callbacks
- test job creation
- top-level code which drives the process.
No change to the output of standalone-generate-dump-flight-runvars.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
return 0
}
-if [ x$buildflight = x ]; then
-
- WANT_XEND=false REVISION_LINUX_OLD=disable
-
- create_build_jobs
-
-else
-
- bfi=$buildflight.
-
-fi
-
job_create_test_filter_callback () {
if [ "$xenarch" = "i386" ]; then return 1; fi
return 0
done
}
+if [ x$buildflight = x ]; then
+
+ WANT_XEND=false REVISION_LINUX_OLD=disable
+
+ create_build_jobs
+
+else
+
+ bfi=$buildflight.
+
+fi
+
test_matrix_iterate
echo $flight
return 0
}
-if [ x$buildflight = x ]; then
-
- create_build_jobs
-
-else
-
- bfi=$buildflight.
-
-fi
-
job_create_test_filter_callback () {
local job=$1; shift
local recipe=$1; shift
do_pvgrub_tests
}
+if [ x$buildflight = x ]; then
+
+ create_build_jobs
+
+else
+
+ bfi=$buildflight.
+
+fi
+
test_matrix_iterate
echo $flight