New Year's Eve bug broke the build

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

New Year's Eve bug broke the build

Stan Silvert
https://github.com/wildfly/wildfly/pull/5653

I'm not sure if this is a bug in the test or a bug in
org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
pretty sure that the build will be working again in a few hours.

Happy New Year!
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Eduardo Martins-2
Same at my end.

—E


On 31 Dec 2013, at 02:17, [hidden email] wrote:

> https://github.com/wildfly/wildfly/pull/5653
>
> I'm not sure if this is a bug in the test or a bug in
> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
> pretty sure that the build will be working again in a few hours.
>
> Happy New Year!
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Eduardo Martins-2
Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.

—E

On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:

> Same at my end.
>
> —E
>
>
> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>
>> https://github.com/wildfly/wildfly/pull/5653
>>
>> I'm not sure if this is a bug in the test or a bug in
>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>> pretty sure that the build will be working again in a few hours.
>>
>> Happy New Year!
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Cheng Fang
Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
failures at end of month) on a yearly scale.

Cheng

On 12/31/13, 9:34 AM, Eduardo Martins wrote:

> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>
> —E
>
> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>
>> Same at my end.
>>
>> —E
>>
>>
>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>
>>> https://github.com/wildfly/wildfly/pull/5653
>>>
>>> I'm not sure if this is a bug in the test or a bug in
>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>> pretty sure that the build will be working again in a few hours.
>>>
>>> Happy New Year!
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Eduardo Martins-2
Will you work on it? If not please let me know and I will take over.

—E

On 31 Dec 2013, at 15:02, Cheng Fang <[hidden email]> wrote:

> Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
> failures at end of month) on a yearly scale.
>
> Cheng
>
> On 12/31/13, 9:34 AM, Eduardo Martins wrote:
>> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>>
>> —E
>>
>> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>>
>>> Same at my end.
>>>
>>> —E
>>>
>>>
>>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>>
>>>> https://github.com/wildfly/wildfly/pull/5653
>>>>
>>>> I'm not sure if this is a bug in the test or a bug in
>>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>>> pretty sure that the build will be working again in a few hours.
>>>>
>>>> Happy New Year!
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Cheng Fang
Feel free to tackle it.

Cheng

On 12/31/13, 10:14 AM, Eduardo Martins wrote:

> Will you work on it? If not please let me know and I will take over.
>
> —E
>
> On 31 Dec 2013, at 15:02, Cheng Fang <[hidden email]> wrote:
>
>> Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
>> failures at end of month) on a yearly scale.
>>
>> Cheng
>>
>> On 12/31/13, 9:34 AM, Eduardo Martins wrote:
>>> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>>>
>>> —E
>>>
>>> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>>>
>>>> Same at my end.
>>>>
>>>> —E
>>>>
>>>>
>>>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>>>
>>>>> https://github.com/wildfly/wildfly/pull/5653
>>>>>
>>>>> I'm not sure if this is a bug in the test or a bug in
>>>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>>>> pretty sure that the build will be working again in a few hours.
>>>>>
>>>>> Happy New Year!
>>>>> _______________________________________________
>>>>> wildfly-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Stan Silvert
In reply to this post by Eduardo Martins-2
On 12/31/2013 9:34 AM, Eduardo Martins wrote:
> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
It showed up yesterday, but this test goes through and tests all the
time zones in the world based on the return value of
TimeZone.getAvailableIDs().

So wherever it happened to be just past midnight on December 31st the
test would fail.  I saw it fail on "Greenwich Mean Time" then in the
next hour it started failing on "Eastern Greenland Time", then after an
hour it failed on "Brasilia Time" and so on.

Now that it is well past midnight, Dec. 31st everywhere in the world, it
always fails on the time zone named "531 GMT-12:00".  At least that's
what I've seen on my box.

>
> —E
>
> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>
>> Same at my end.
>>
>> —E
>>
>>
>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>
>>> https://github.com/wildfly/wildfly/pull/5653
>>>
>>> I'm not sure if this is a bug in the test or a bug in
>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>> pretty sure that the build will be working again in a few hours.
>>>
>>> Happy New Year!
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Eduardo Martins-2
The issue seems to be just a test bug that does not handles well the last and first couple of days for each.


Cheng, dunno if the JBCTS issue is relative, please check.

—E

On 31 Dec 2013, at 17:49, [hidden email] wrote:

On 12/31/2013 9:34 AM, Eduardo Martins wrote:
Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
It showed up yesterday, but this test goes through and tests all the
time zones in the world based on the return value of
TimeZone.getAvailableIDs().

So wherever it happened to be just past midnight on December 31st the
test would fail.  I saw it fail on "Greenwich Mean Time" then in the
next hour it started failing on "Eastern Greenland Time", then after an
hour it failed on "Brasilia Time" and so on.

Now that it is well past midnight, Dec. 31st everywhere in the world, it
always fails on the time zone named "531 GMT-12:00".  At least that's
what I've seen on my box.

—E

On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:

Same at my end.

—E


On 31 Dec 2013, at 02:17, [hidden email] wrote:

https://github.com/wildfly/wildfly/pull/5653

I'm not sure if this is a bug in the test or a bug in
org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
pretty sure that the build will be working again in a few hours.

Happy New Year!
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

David Lloyd-2
In reply to this post by Cheng Fang
We should not be relying on the current date/calendar to change the
outcome of any test.  We should be using some type of "pre-cooked" clock
which is set to specific test dates for these tests in particular.

On 12/31/2013 09:46 AM, Cheng Fang wrote:

> Feel free to tackle it.
>
> Cheng
>
> On 12/31/13, 10:14 AM, Eduardo Martins wrote:
>> Will you work on it? If not please let me know and I will take over.
>>
>> —E
>>
>> On 31 Dec 2013, at 15:02, Cheng Fang <[hidden email]> wrote:
>>
>>> Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
>>> failures at end of month) on a yearly scale.
>>>
>>> Cheng
>>>
>>> On 12/31/13, 9:34 AM, Eduardo Martins wrote:
>>>> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>>>>
>>>> —E
>>>>
>>>> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>>>>
>>>>> Same at my end.
>>>>>
>>>>> —E
>>>>>
>>>>>
>>>>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>>>>
>>>>>> https://github.com/wildfly/wildfly/pull/5653
>>>>>>
>>>>>> I'm not sure if this is a bug in the test or a bug in
>>>>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>>>>> pretty sure that the build will be working again in a few hours.
>>>>>>
>>>>>> Happy New Year!
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>> _______________________________________________
>>>>> wildfly-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


--
- DML
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

Eduardo Martins-2
IMO it’s good to use actual dates and timezones, this way we may get bugs that only show with specific dates ;-)

Anyway, the PR is merged, it should not be an issue anymore.

—E

On 02 Jan 2014, at 19:02, David M. Lloyd <[hidden email]> wrote:

> We should not be relying on the current date/calendar to change the
> outcome of any test.  We should be using some type of "pre-cooked" clock
> which is set to specific test dates for these tests in particular.
>
> On 12/31/2013 09:46 AM, Cheng Fang wrote:
>> Feel free to tackle it.
>>
>> Cheng
>>
>> On 12/31/13, 10:14 AM, Eduardo Martins wrote:
>>> Will you work on it? If not please let me know and I will take over.
>>>
>>> —E
>>>
>>> On 31 Dec 2013, at 15:02, Cheng Fang <[hidden email]> wrote:
>>>
>>>> Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
>>>> failures at end of month) on a yearly scale.
>>>>
>>>> Cheng
>>>>
>>>> On 12/31/13, 9:34 AM, Eduardo Martins wrote:
>>>>> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>>>>>
>>>>> —E
>>>>>
>>>>> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>>>>>
>>>>>> Same at my end.
>>>>>>
>>>>>> —E
>>>>>>
>>>>>>
>>>>>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>>>>>
>>>>>>> https://github.com/wildfly/wildfly/pull/5653
>>>>>>>
>>>>>>> I'm not sure if this is a bug in the test or a bug in
>>>>>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>>>>>> pretty sure that the build will be working again in a few hours.
>>>>>>>
>>>>>>> Happy New Year!
>>>>>>> _______________________________________________
>>>>>>> wildfly-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>> _______________________________________________
>>>>> wildfly-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
>
> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

jtgreene
Administrator
I have to agree with David on this one. It’s fine to use actual dates and timezones. It’s bad to have the time the test as ran be an input into the test.
On Jan 2, 2014, at 1:04 PM, Eduardo Martins <[hidden email]> wrote:

> IMO it’s good to use actual dates and timezones, this way we may get bugs that only show with specific dates ;-)
>
> Anyway, the PR is merged, it should not be an issue anymore.
>
> —E
>
> On 02 Jan 2014, at 19:02, David M. Lloyd <[hidden email]> wrote:
>
>> We should not be relying on the current date/calendar to change the
>> outcome of any test.  We should be using some type of "pre-cooked" clock
>> which is set to specific test dates for these tests in particular.
>>
>> On 12/31/2013 09:46 AM, Cheng Fang wrote:
>>> Feel free to tackle it.
>>>
>>> Cheng
>>>
>>> On 12/31/13, 10:14 AM, Eduardo Martins wrote:
>>>> Will you work on it? If not please let me know and I will take over.
>>>>
>>>> —E
>>>>
>>>> On 31 Dec 2013, at 15:02, Cheng Fang <[hidden email]> wrote:
>>>>
>>>>> Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
>>>>> failures at end of month) on a yearly scale.
>>>>>
>>>>> Cheng
>>>>>
>>>>> On 12/31/13, 9:34 AM, Eduardo Martins wrote:
>>>>>> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>>>>>>
>>>>>> —E
>>>>>>
>>>>>> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>>>>>>
>>>>>>> Same at my end.
>>>>>>>
>>>>>>> —E
>>>>>>>
>>>>>>>
>>>>>>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>>>>>>
>>>>>>>> https://github.com/wildfly/wildfly/pull/5653
>>>>>>>>
>>>>>>>> I'm not sure if this is a bug in the test or a bug in
>>>>>>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>>>>>>> pretty sure that the build will be working again in a few hours.
>>>>>>>>
>>>>>>>> Happy New Year!
>>>>>>>> _______________________________________________
>>>>>>>> wildfly-dev mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>>> _______________________________________________
>>>>>>> wildfly-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>> _______________________________________________
>>>>> wildfly-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>
>>
>> --
>> - DML
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: New Year's Eve bug broke the build

jtgreene
Administrator
To illustrate why this is bad, its going to be a whole year from now until we know if the “bug” is fixed, and thats assuming the test suite is even ran that day. Perhaps for some reason it’s not.

On Jan 2, 2014, at 1:53 PM, Jason Greene <[hidden email]> wrote:

> I have to agree with David on this one. It’s fine to use actual dates and timezones. It’s bad to have the time the test as ran be an input into the test.
> On Jan 2, 2014, at 1:04 PM, Eduardo Martins <[hidden email]> wrote:
>
>> IMO it’s good to use actual dates and timezones, this way we may get bugs that only show with specific dates ;-)
>>
>> Anyway, the PR is merged, it should not be an issue anymore.
>>
>> —E
>>
>> On 02 Jan 2014, at 19:02, David M. Lloyd <[hidden email]> wrote:
>>
>>> We should not be relying on the current date/calendar to change the
>>> outcome of any test.  We should be using some type of "pre-cooked" clock
>>> which is set to specific test dates for these tests in particular.
>>>
>>> On 12/31/2013 09:46 AM, Cheng Fang wrote:
>>>> Feel free to tackle it.
>>>>
>>>> Cheng
>>>>
>>>> On 12/31/13, 10:14 AM, Eduardo Martins wrote:
>>>>> Will you work on it? If not please let me know and I will take over.
>>>>>
>>>>> —E
>>>>>
>>>>> On 31 Dec 2013, at 15:02, Cheng Fang <[hidden email]> wrote:
>>>>>
>>>>>> Looks similar to https://issues.jboss.org/browse/JBCTS-1253 (ejb3 timer
>>>>>> failures at end of month) on a yearly scale.
>>>>>>
>>>>>> Cheng
>>>>>>
>>>>>> On 12/31/13, 9:34 AM, Eduardo Martins wrote:
>>>>>>> Yet this already shown up yesterday, so not sure it’s due to new year, is anyone looking at it please reply, otherwise I will have a look at it.
>>>>>>>
>>>>>>> —E
>>>>>>>
>>>>>>> On 31 Dec 2013, at 14:30, Eduardo Martins <[hidden email]> wrote:
>>>>>>>
>>>>>>>> Same at my end.
>>>>>>>>
>>>>>>>> —E
>>>>>>>>
>>>>>>>>
>>>>>>>> On 31 Dec 2013, at 02:17, [hidden email] wrote:
>>>>>>>>
>>>>>>>>> https://github.com/wildfly/wildfly/pull/5653
>>>>>>>>>
>>>>>>>>> I'm not sure if this is a bug in the test or a bug in
>>>>>>>>> org.jboss.as.ejb3.timerservice.schedule.CalendarBasedTimeout.  But I'm
>>>>>>>>> pretty sure that the build will be working again in a few hours.
>>>>>>>>>
>>>>>>>>> Happy New Year!
>>>>>>>>> _______________________________________________
>>>>>>>>> wildfly-dev mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>>>> _______________________________________________
>>>>>>>> wildfly-dev mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>>> _______________________________________________
>>>>>>> wildfly-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>
>>>
>>> --
>>> - DML
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev