mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Christoph Rüdiger" <christoph@ruediger.engineering>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Errors when running in Jenkins
Date: Tue, 10 May 2016 17:04:00 +0200	[thread overview]
Message-ID: <5731F860.9020507@ruediger.engineering> (raw)

Hello,

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?

Thanks,
Christoph

-- 
rüdiger.engineering
Christoph Rüdiger
Düsseldorfer Str. 12
45145 Essen
Germany

phone: +49 201 458 478 58
PGP key: 0xE513B105

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2016-05-10 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 15:04 Christoph Rüdiger [this message]
2016-05-12  9:07 ` Michael Olbrich
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=5731F860.9020507@ruediger.engineering \
    --to=christoph@ruediger.engineering \
    --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