From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] travis-ci: Do not make buildman warnings fatal
Date: Fri, 21 Oct 2016 09:39:28 +0200 [thread overview]
Message-ID: <5809C630.8030202@denx.de> (raw)
In-Reply-To: <1476991566-2989-5-git-send-email-trini@konsulko.com>
Hello Tom,
Am 20.10.2016 um 21:26 schrieb Tom Rini:
> We currently will always see a number of warnings due to device tree
> issues. These (and other warnings) should not make the build be marked
> as failure so catch exit status 129 specifically and return 0 in that
> case.
>
> Cc: Heiko Schocher <hs@denx.de>
> Signed-off-by: Tom Rini <trini@konsulko.com>
You mean here this "Warning (unit_address_vs_reg):" warnings?
IIRC I posted some month ago a patch, which suppress them ... the
patch was rejected, with the plausible reason, that we should fix
this issues ... so I started and posted some dts fix patches, also
rejected with the reason that this should come from linux syncs ...
Hmm.. do we syncs for our DTS files with linux?
Nevertheless: we should at least fix this for travis, so:
Reviewed-by: Heiko Schocher <hs@denx.de>
bye,
Heiko
> ---
> .travis.yml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/.travis.yml b/.travis.yml
> index 2f1d05d443f5..d93efe02b0b1 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -69,8 +69,15 @@ script:
> - if [[ "${TEST_CMD}" != "" ]]; then
> ${TEST_CMD};
> fi
> + # Exit code 129 means warnings only.
> - if [[ "${BUILDMAN}" != "" ]]; then
> + set +e;
> tools/buildman/buildman ${BUILDMAN};
> + if [[ "$?" == "0" || "$?" == "129" ]]; then
> + exit 0;
> + else
> + exit $?;
> + fi
> fi
>
> matrix:
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-10-21 7:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:25 [U-Boot] [PATCH 0/8] Various travis-ci improvements Tom Rini
2016-10-20 19:25 ` [U-Boot] [PATCH 1/8] test/py: ensure a log section exists for skipped tests Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 2/8] travis-ci: Switch to Ubuntu 14.04 'Trusty Tahr' Tom Rini
2016-10-21 7:27 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 3/8] travis-ci: Use a git URI for dtc.git Tom Rini
2016-10-21 7:32 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 4/8] travis-ci: Do not make buildman warnings fatal Tom Rini
2016-10-21 7:39 ` Heiko Schocher [this message]
2016-10-21 11:19 ` Tom Rini
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 5/8] travis-ci: Update toolchain and buildman usage Tom Rini
2016-10-21 7:40 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 6/8] travis-ci: Add more architectures Tom Rini
2016-10-21 7:41 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 7/8] travis-ci: Drop 'TEST_CMD' Tom Rini
2016-10-21 7:54 ` Heiko Schocher
2016-10-24 15:23 ` Tom Rini
2016-10-20 19:26 ` [U-Boot] [PATCH 8/8] travis-ci: Add test.py for various qemu platforms Tom Rini
2016-10-20 19:40 ` [U-Boot] [PATCH v2 " Tom Rini
2016-10-21 18:24 ` Stephen Warren
2016-10-22 12:56 ` Tom Rini
2016-10-24 22:21 ` Stephen Warren
2016-10-24 22:46 ` Tom Rini
2016-10-24 15:23 ` Tom Rini
2016-10-21 9:22 ` [U-Boot] [PATCH " Heiko Schocher
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=5809C630.8030202@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox