[wildfly-dev] New Year's Eve bug broke the build
ssilvert at redhat.com
ssilvert at redhat.com
Tue Dec 31 12:49:41 EST 2013
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 <emartins at redhat.com> wrote:
>
>> Same at my end.
>>
>> —E
>>
>>
>> On 31 Dec 2013, at 02:17, ssilvert at redhat.com 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
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
More information about the wildfly-dev
mailing list