Am 12.05.16 um 11:07 schrieb Michael Olbrich:
> 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.
Thank you for the explanation. I will ignore them, too. :-)
> I don't know anything about the other occurrences, but I would expect
> something similar.
I will have a look at the respective rule files. But from the error
message I expect something similar.
Regards,
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
[email protected]
