You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2019/02/20 22:00:23 UTC
Strange build errors
Hi all,
I just noticed that again one of my commits failed even if I did the full build.
An investigation showed that it exited somewhere in the API module.
I have seen this occasionally and I think it might be related to concurrent builds.
Cause I get these random failures whenever we have concurrent build jobs running.
Would really like to find out the reason for this.
So if you see any failures with the build complaining about some exit code, try simply re-running the build.
Chris
Re: Strange build errors
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Could this be related to some ulimit stuff?
(Also observed something like that in our env, I think).
Am 21.02.19, 09:32 schrieb "Christofer Dutz" <ch...@c-ware.de>:
I would assume it's related to file handles, however I don't really know where to find out why the os is killing the jobs. Perhaps increasing the max open file handles will help.
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Tim Mitsch <t....@pragmaticindustries.de>
Sent: Thursday, February 21, 2019 8:40:14 AM
To: dev@plc4x.apache.org
Subject: Re: Strange build errors
Hi Chris
Thanks for the info ... i first thought it was because of my fix to odd-size arrays - but verify succeeded without any problems.
I'm neither build nor jenkins pro ... so i can't help much - but if i see anything i'll report.
Best
Tim
Am 20.02.19, 23:00 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
I just noticed that again one of my commits failed even if I did the full build.
An investigation showed that it exited somewhere in the API module.
I have seen this occasionally and I think it might be related to concurrent builds.
Cause I get these random failures whenever we have concurrent build jobs running.
Would really like to find out the reason for this.
So if you see any failures with the build complaining about some exit code, try simply re-running the build.
Chris
Re: Strange build errors
Posted by Christofer Dutz <ch...@c-ware.de>.
I would assume it's related to file handles, however I don't really know where to find out why the os is killing the jobs. Perhaps increasing the max open file handles will help.
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Tim Mitsch <t....@pragmaticindustries.de>
Sent: Thursday, February 21, 2019 8:40:14 AM
To: dev@plc4x.apache.org
Subject: Re: Strange build errors
Hi Chris
Thanks for the info ... i first thought it was because of my fix to odd-size arrays - but verify succeeded without any problems.
I'm neither build nor jenkins pro ... so i can't help much - but if i see anything i'll report.
Best
Tim
Am 20.02.19, 23:00 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
I just noticed that again one of my commits failed even if I did the full build.
An investigation showed that it exited somewhere in the API module.
I have seen this occasionally and I think it might be related to concurrent builds.
Cause I get these random failures whenever we have concurrent build jobs running.
Would really like to find out the reason for this.
So if you see any failures with the build complaining about some exit code, try simply re-running the build.
Chris
Re: Strange build errors
Posted by Tim Mitsch <t....@pragmaticindustries.de>.
Hi Chris
Thanks for the info ... i first thought it was because of my fix to odd-size arrays - but verify succeeded without any problems.
I'm neither build nor jenkins pro ... so i can't help much - but if i see anything i'll report.
Best
Tim
Am 20.02.19, 23:00 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
I just noticed that again one of my commits failed even if I did the full build.
An investigation showed that it exited somewhere in the API module.
I have seen this occasionally and I think it might be related to concurrent builds.
Cause I get these random failures whenever we have concurrent build jobs running.
Would really like to find out the reason for this.
So if you see any failures with the build complaining about some exit code, try simply re-running the build.
Chris