3:58 a.m.
Hi,
I see that short timeout (500 ms) is an often cause of random failures
in CI. The original issue (ISPN-4772) raised this from 100 to 500; could
we increase this on CI even further, to, say, 3 seconds? It's
configurable via a sys property
infinispan.test.shortTimeoutMillis
Radim
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
3:59 a.m.
Sounds good...
Sadly our build infrastructure is not very fast...
On Mon, Mar 27, 2017 at 10:58 AM Radim Vansa <rvansa(a)redhat.com> wrote:
Hi,
I see that short timeout (500 ms) is an often cause of random failures
in CI. The original issue (ISPN-4772) raised this from 100 to 500; could
we increase this on CI even further, to, say, 3 seconds? It's
configurable via a sys property
infinispan.test.shortTimeoutMillis
Radim
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
4:25 a.m.
Radim, are you seeing this in the regular builds too, or just in the
TRACE build?
Dan
On Mon, Mar 27, 2017 at 11:59 AM, Sebastian Laskawiec
<slaskawi(a)redhat.com> wrote:
Sounds good...
Sadly our build infrastructure is not very fast...
On Mon, Mar 27, 2017 at 10:58 AM Radim Vansa <rvansa(a)redhat.com> wrote:
>
> Hi,
>
> I see that short timeout (500 ms) is an often cause of random failures
> in CI. The original issue (ISPN-4772) raised this from 100 to 500; could
> we increase this on CI even further, to, say, 3 seconds? It's
> configurable via a sys property
>
> infinispan.test.shortTimeoutMillis
>
> Radim
>
> --
> Radim Vansa <rvansa(a)redhat.com>
> JBoss Performance Team
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
5:35 a.m.
In regular ones [1] - see SyncLockingTest
Btw., how do I enable TRACE build in CI?
[1] http://ci.infinispan.org/viewLog.html?buildId=53604&buildTypeId=bt9
On 03/27/2017 11:25 AM, Dan Berindei wrote:
Radim, are you seeing this in the regular builds too, or just in the
TRACE build?
Dan
On Mon, Mar 27, 2017 at 11:59 AM, Sebastian Laskawiec
<slaskawi(a)redhat.com> wrote:
> Sounds good...
>
> Sadly our build infrastructure is not very fast...
>
> On Mon, Mar 27, 2017 at 10:58 AM Radim Vansa <rvansa(a)redhat.com> wrote:
>> Hi,
>>
>> I see that short timeout (500 ms) is an often cause of random failures
>> in CI. The original issue (ISPN-4772) raised this from 100 to 500; could
>> we increase this on CI even further, to, say, 3 seconds? It's
>> configurable via a sys property
>>
>> infinispan.test.shortTimeoutMillis
>>
>> Radim
>>
>> --
>> Radim Vansa <rvansa(a)redhat.com>
>> JBoss Performance Team
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
6:19 a.m.
On Mon, Mar 27, 2017 at 1:35 PM, Radim Vansa <rvansa(a)redhat.com> wrote:
In regular ones [1] - see SyncLockingTest
shortTimeoutMillis() doesn't really fit here, it's intended for tests
that expect the operation to time out. I probably used it only because
the cache was already configured with 500ms.
OTOH there's no contention here, except for the fact that
TxCompletionNotification is async, so 500ms should be plenty even on
our puny CI agents...
Btw., how do I enable TRACE build in CI?
I meant this build:
http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp...
You can also enable trace logging in custom builds (the Run... button)
by changing the maven_opts.log.debug parameter to include
log4j2-trace.xml instead of log4j2.xml, it's just that there's no
filtering step so the logs will be quite big.
[1] http://ci.infinispan.org/viewLog.html?buildId=53604&buildTypeId=bt9
On 03/27/2017 11:25 AM, Dan Berindei wrote:
> Radim, are you seeing this in the regular builds too, or just in the
> TRACE build?
>
> Dan
>
>
> On Mon, Mar 27, 2017 at 11:59 AM, Sebastian Laskawiec
> <slaskawi(a)redhat.com> wrote:
>> Sounds good...
>>
>> Sadly our build infrastructure is not very fast...
>>
>> On Mon, Mar 27, 2017 at 10:58 AM Radim Vansa <rvansa(a)redhat.com> wrote:
>>> Hi,
>>>
>>> I see that short timeout (500 ms) is an often cause of random failures
>>> in CI. The original issue (ISPN-4772) raised this from 100 to 500; could
>>> we increase this on CI even further, to, say, 3 seconds? It's
>>> configurable via a sys property
>>>
>>> infinispan.test.shortTimeoutMillis
>>>
>>> Radim
>>>
>>> --
>>> Radim Vansa <rvansa(a)redhat.com>
>>> JBoss Performance Team
>>>
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
2638
days inactive
2639
days old
infinispan-dev@lists.jboss.org
4 comments
3 participants
participants (3)
-
Dan Berindei -
Radim Vansa -
Sebastian Laskawiec