From: Ian Jackson <iwj@xenproject.org>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <iwj@xenproject.org>
Subject: [OSSTEST PATCH] cr-daily-branch: Sort out retest build reuse
Date: Fri, 13 Nov 2020 17:39:52 +0000 [thread overview]
Message-ID: <20201113173952.29800-1-iwj@xenproject.org> (raw)
Retest flights ought to reuse precisely the builds from the flight
which prompts the retests.
mg-adjust-flight-makexrefs is the wrong tool for this job. It can
often leave the retry flights with no build jobs and no references to
the main flights' build jobs, so the results are just broken jobs.
Signed-off-by: Ian Jackson <iwj@xenproject.org>
---
cr-daily-branch | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/cr-daily-branch b/cr-daily-branch
index e54ca227..6ec3aa62 100755
--- a/cr-daily-branch
+++ b/cr-daily-branch
@@ -529,9 +529,8 @@ END
$retry_jobs
)
- ./mg-adjust-flight-makexrefs -v $rflight \
- --branch=$branch --revision-osstest=$narness_rev \
- '^build-*' --debug --blessings=real
+ ./cs-adjust-flight -D $rflight \
+ runvar-build-set . . "^$rflight\\." $flight.
if [ "${OSSTEST_SIMULATE_FAIL_RETRY+y}" = y ]; then
export OSSTEST_SIMULATE_FAIL="${OSSTEST_SIMULATE_FAIL_RETRY}"
--
2.20.1
reply other threads:[~2020-11-13 17:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201113173952.29800-1-iwj@xenproject.org \
--to=iwj@xenproject.org \
--cc=xen-devel@lists.xenproject.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.