From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Errors when running in Jenkins
Date: Thu, 12 May 2016 11:07:01 +0200 [thread overview]
Message-ID: <20160512090701.GF17094@pengutronix.de> (raw)
In-Reply-To: <5731F860.9020507@ruediger.engineering>
On Tue, May 10, 2016 at 05:04:00PM +0200, Christoph Rüdiger wrote:
> I've setup a few ptxdist jobs in our Jenkins server and right now I'm
> getting a bunch of error messages consisting of these two lines:
>
> yes: standard output: Broken pipe
> yes: write error
>
> They always occur before ptxdist is actually hitting the first target
> (download, extract, compile, whatever it is). Additionally, in some
> targets they can be observed as well. They cannot be observed when
> running the ptxdist command on the same machine in the same workspace
> with the Jenkins user but as manual command in an SSH session.
>
> However, the ptxdist call runs well (exit code 0) and from roughly
> examining the built images, I cannot see what is missing or broken.
>
> I'm far away from being a bash guru. Can someone explain to me what this
> is about?
>
> Do I need to care about? And if so, how can I get rid of these errors?
The error at the beginning comes from ptxd_kconfig() in
scripts/libptxdist.sh:
...
yes "" | "${conf}" --writedepend "${file_kconfig}" &&
...
I think that's some stange race condition when there is no tty. We ignore
the error for 'yes' here, but not errors from '${conf}' so that's ok and
should work as expected.
I don't know anything about the other occurrences, but I would expect
something similar.
Regards,
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-05-12 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 15:04 Christoph Rüdiger
2016-05-12 9:07 ` Michael Olbrich [this message]
2016-05-12 10:19 ` Christoph Rüdiger
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=20160512090701.GF17094@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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