You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2012/10/21 00:34:19 UTC
Jenkins builds
So for once instead of random and otherwise impossible to reproduce unit test failures I noticed an explicit mention of low PermGen memory. So I set these Maven args for the build:
-Xmx512m -XX:MaxPermSize=128m
That fixed 3.1 build: https://builds.apache.org/job/Cayenne-31/23/
But not 3.2: https://builds.apache.org/job/Cayenne-trunk/776/
I also suspect that enabling "Use private Maven repository" should help with another common class of problems (but not the one at hand for 3.2), but figured we'll wait till the next relevant failure before changing this config.
Andrus
RE: Jenkins builds
Posted by "Durchholz, Joachim" <Jo...@hennig-fahrzeugteile.de>.
> Will need to test the performance of such remote setup though.
It would be an interesting data point in itself whether such a setup would be fast or slow.
Re: Jenkins builds
Posted by Andrus Adamchik <an...@objectstyle.org>.
The DB's that we'd like to test with are MySQL, PostgreSQL, MSSQL (express edition will work) and Oracle. Maybe also some version of DB2. If Apache can't provide the servers for these, maybe we'll host them outside on the cloud somewhere and start/stop OS images on demand. Will need to test the performance of such remote setup though.
Not as important as the site migration at this point, but would be cool to have.
Andrus
On Oct 22, 2012, at 12:43 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> It also reminds me that I need to have another go at getting MS-SQL builds working. Any other databases we should target?
>
> Ari
>
>
> On 21/10/12 11:05pm, Andrus Adamchik wrote:
>> Just switched to the private repo mode to ensure ongoing build sanity (and to be able to browse "workspace" Maven deps via the web UI). Also fixed DB cleanup code in a few unit tests that resulted in random failures not related to the main code.
>>
>> Finally and most importantly identified and fix a real (and a very annoying) race condition: CAY-1749.
>>
>> So after all there was nothing unexplainable or mysterious about our failures and now we seem to have a stream of successful builds on both 3.1 and 3.2. This makes me very happy :)
>>
>> What also delights me is that CAY-1749 issue proved that Jenkins can sometimes point to otherwise undetectable race conditions just by the virtue of the large number of builds shuffled across the servers, and collocated with other Apache project builds. Maybe we should take better advantage of that and write more unit tests specifically emulating concurrent scenarios.
>>
>> Andrus
>>
>>
>> On Oct 21, 2012, at 1:34 AM, Andrus Adamchik <an...@objectstyle.org> wrote:
>>
>>> So for once instead of random and otherwise impossible to reproduce unit test failures I noticed an explicit mention of low PermGen memory. So I set these Maven args for the build:
>>>
>>> -Xmx512m -XX:MaxPermSize=128m
>>>
>>> That fixed 3.1 build: https://builds.apache.org/job/Cayenne-31/23/
>>> But not 3.2: https://builds.apache.org/job/Cayenne-trunk/776/
>>>
>>> I also suspect that enabling "Use private Maven repository" should help with another common class of problems (but not the one at hand for 3.2), but figured we'll wait till the next relevant failure before changing this config.
>>>
>>> Andrus
>>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Jenkins builds
Posted by Aristedes Maniatis <ar...@maniatis.org>.
It also reminds me that I need to have another go at getting MS-SQL builds working. Any other databases we should target?
Ari
On 21/10/12 11:05pm, Andrus Adamchik wrote:
> Just switched to the private repo mode to ensure ongoing build sanity (and to be able to browse "workspace" Maven deps via the web UI). Also fixed DB cleanup code in a few unit tests that resulted in random failures not related to the main code.
>
> Finally and most importantly identified and fix a real (and a very annoying) race condition: CAY-1749.
>
> So after all there was nothing unexplainable or mysterious about our failures and now we seem to have a stream of successful builds on both 3.1 and 3.2. This makes me very happy :)
>
> What also delights me is that CAY-1749 issue proved that Jenkins can sometimes point to otherwise undetectable race conditions just by the virtue of the large number of builds shuffled across the servers, and collocated with other Apache project builds. Maybe we should take better advantage of that and write more unit tests specifically emulating concurrent scenarios.
>
> Andrus
>
>
> On Oct 21, 2012, at 1:34 AM, Andrus Adamchik <an...@objectstyle.org> wrote:
>
>> So for once instead of random and otherwise impossible to reproduce unit test failures I noticed an explicit mention of low PermGen memory. So I set these Maven args for the build:
>>
>> -Xmx512m -XX:MaxPermSize=128m
>>
>> That fixed 3.1 build: https://builds.apache.org/job/Cayenne-31/23/
>> But not 3.2: https://builds.apache.org/job/Cayenne-trunk/776/
>>
>> I also suspect that enabling "Use private Maven repository" should help with another common class of problems (but not the one at hand for 3.2), but figured we'll wait till the next relevant failure before changing this config.
>>
>> Andrus
>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Jenkins builds
Posted by Andrus Adamchik <an...@objectstyle.org>.
Just switched to the private repo mode to ensure ongoing build sanity (and to be able to browse "workspace" Maven deps via the web UI). Also fixed DB cleanup code in a few unit tests that resulted in random failures not related to the main code.
Finally and most importantly identified and fix a real (and a very annoying) race condition: CAY-1749.
So after all there was nothing unexplainable or mysterious about our failures and now we seem to have a stream of successful builds on both 3.1 and 3.2. This makes me very happy :)
What also delights me is that CAY-1749 issue proved that Jenkins can sometimes point to otherwise undetectable race conditions just by the virtue of the large number of builds shuffled across the servers, and collocated with other Apache project builds. Maybe we should take better advantage of that and write more unit tests specifically emulating concurrent scenarios.
Andrus
On Oct 21, 2012, at 1:34 AM, Andrus Adamchik <an...@objectstyle.org> wrote:
> So for once instead of random and otherwise impossible to reproduce unit test failures I noticed an explicit mention of low PermGen memory. So I set these Maven args for the build:
>
> -Xmx512m -XX:MaxPermSize=128m
>
> That fixed 3.1 build: https://builds.apache.org/job/Cayenne-31/23/
> But not 3.2: https://builds.apache.org/job/Cayenne-trunk/776/
>
> I also suspect that enabling "Use private Maven repository" should help with another common class of problems (but not the one at hand for 3.2), but figured we'll wait till the next relevant failure before changing this config.
>
> Andrus