[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [OSSTEST PATCH] README.dev: Say how to do a commissioning flight for a new architecture
Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> --- README.dev | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.dev b/README.dev index dc0dafd..37e2953 100644 --- a/README.dev +++ b/README.dev @@ -132,6 +132,13 @@ If that works, a more thorough test: This should show no regressions. (Or, at least, none that are a cause for concern.) +For a new architecture, there may not be an existing flight with +suitable jobs. In that case, something like this can be useful: + + $ OSSTEST_BLESSING=commission-mudcake DAILY_BRANCH_PREEXEC_HOOK=false OSSTEST_BASELINES_ONLY=y ./cr-daily-branch xen-unstable + +You'll need to fish the flight number out of the debug spew. + Bless ----- -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |