From: Bob Cochran <yocto@mindchasers.com>
To: yocto@yoctoproject.org
Subject: [yocto-autobuilder] [PATCH] ppc & mips names are switched for builders
Date: Wed, 29 Feb 2012 13:05:51 -0500 [thread overview]
Message-ID: <4F4E68FF.8090600@mindchasers.com> (raw)
I have noticed in the nightly buildbot failure reports for ppc & mips
that the build names are switched (e.g., nightly-mips triggers the
nightly-ppc build and vice versa).
The name and builderNames appear to be switched in yoctoABConfig.py, and
I think this patch will correct this one.
Signed-off-by: Robert Cochran<yocto@mindchasers.com>
---
yocto-master/yoctoABConfig.py | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/yocto-master/yoctoABConfig.py b/yocto-master/yoctoABConfig.py
index 0d4ed13..2e0cf27 100644
--- a/yocto-master/yoctoABConfig.py
+++ b/yocto-master/yoctoABConfig.py
@@ -864,8 +864,8 @@ yocto_builders.append(b65)
yocto_sched.append(triggerable.Triggerable(name="nightly-x86",
builderNames=["nightly-x86"]))
yocto_sched.append(triggerable.Triggerable(name="nightly-x86-64",
builderNames=["nightly-x86-64"]))
yocto_sched.append(triggerable.Triggerable(name="nightly-arm",
builderNames=["nightly-arm"]))
-yocto_sched.append(triggerable.Triggerable(name="nightly-ppc",
builderNames=["nightly-mips"]))
-yocto_sched.append(triggerable.Triggerable(name="nightly-mips",
builderNames=["nightly-ppc"]))
+yocto_sched.append(triggerable.Triggerable(name="nightly-mips",
builderNames=["nightly-mips"]))
+yocto_sched.append(triggerable.Triggerable(name="nightly-ppc",
builderNames=["nightly-ppc"]))
yocto_sched.append(triggerable.Triggerable(name="eclipse-plugin",
builderNames=["eclipse-plugin"]))
################################################################################
--
1.7.5.4
next reply other threads:[~2012-02-29 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 18:05 Bob Cochran [this message]
2012-02-29 21:37 ` [yocto-autobuilder] [PATCH] ppc & mips names are switched for builders Flanagan, Elizabeth
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=4F4E68FF.8090600@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=yocto@yoctoproject.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.