From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [tisdk-build-scripts][PATCH] bitbake-test-sdk-image: preserve bitbake-cookerdaemon.log
Date: Thu, 10 May 2018 11:47:34 -0400 [thread overview]
Message-ID: <20180510154734.GI31698@edge> (raw)
In-Reply-To: <1525962988-28642-1-git-send-email-j-stiffler@ti.com>
On Thu, May 10, 2018 at 10:36:28AM -0400, Jacob Stiffler wrote:
> * When stdout/stderr is piped, if there is an error during parsing,
> all that will be printed is "Unable to start bitbake server"
> * The bitbake-cookerdaemon.log will contain the error message, so
> preserve it in the LOG_DIR.
>
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
> lib/oesdk/bitbake-test-sdk-image | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/oesdk/bitbake-test-sdk-image b/lib/oesdk/bitbake-test-sdk-image
> index f17b594..de081cf 100644
> --- a/lib/oesdk/bitbake-test-sdk-image
> +++ b/lib/oesdk/bitbake-test-sdk-image
> @@ -465,6 +465,9 @@ bitbake_sdk_images(){
> fi
> done
>
> + # Move the bitbake-cooker.log as some errors may get hidden in there.
> + mv $build_dir/bitbake-cookerdaemon.log $LOG_DIR/$m-bitbake-cookerdaemon.log
What happens if the file doesn't exist?
> # Only run the build testing if the status of the above builds
> # was "pass"
> if [ "$build_status" == "pass" ]
> --
> 1.9.1
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
next prev parent reply other threads:[~2018-05-10 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 14:36 [tisdk-build-scripts][PATCH] bitbake-test-sdk-image: preserve bitbake-cookerdaemon.log Jacob Stiffler
2018-05-10 15:47 ` Denys Dmytriyenko [this message]
2018-05-10 16:15 ` Jacob Stiffler
2018-05-10 16:17 ` Denys Dmytriyenko
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=20180510154734.GI31698@edge \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=meta-arago@arago-project.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.