From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: [PATCH OSSTEST 0/5] make-flight job filter cleanups
Date: Tue, 17 Nov 2015 17:13:13 +0000 [thread overview]
Message-ID: <1447780393.301.51.camel@citrix.com> (raw)
The mechanisms for omitting certain archs from jobs are inconsistently
applied to build vs test jobs.
This series tries to tidy that up somewhat.
I've check the output of standalone-generate-dump-flight-runvars at each
step (i.e. covering the main make-flight).
I also did a before and after the entire flight check for the branches
handled by make-distro-flight and there was no difference (as expected).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2015-11-17 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 17:13 Ian Campbell [this message]
2015-11-17 17:13 ` [PATCH OSSTEST 1/5] mg-adjust-flight-makexrefs: Make a nop in Standalone mode Ian Campbell
2015-11-25 11:26 ` Ian Jackson
2015-11-17 17:13 ` [PATCH OSSTEST 2/5] mfi-common: Drop armhf build jobs on older linux-* branches Ian Campbell
2015-11-25 11:26 ` Ian Jackson
2015-11-17 17:13 ` [PATCH OSSTEST 3/5] make-*flight: Reorder Ian Campbell
2015-11-25 11:26 ` Ian Jackson
2015-11-17 17:13 ` [PATCH OSSTEST 4/5] make-flight: consolidate branch_filter_callback for builds and tests Ian Campbell
2015-11-17 17:13 ` [PATCH OSSTEST 5/5] make-flight: move in-lined branch vs arch filtering into callbacks Ian Campbell
2015-11-25 11:30 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447780393.301.51.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.