Fixed and committed - standardized the timezone to UTC in
the ISO8601DateParser and updated the test accordingly (it was using
the timezone of the build machine and the test had hardcoded the
EST-relative answer...)

Once we shake out the initial kinks of the first couple of days, we will
start ticketing everything.

On Tue, Jul 12, 2016 at 1:10 PM, Ellison Anne Williams <
[email protected]> wrote:

> Hi Billie -
>
> I'll check it out...
>
> Ellison Anne
>
> On Tue, Jul 12, 2016 at 12:33 PM, Billie Rinaldi <[email protected]>
> wrote:
>
>> I get one test failure in ISO8601DateParserTest:
>>
>> java.lang.AssertionError: expected:<1456028945000> but was:<1456039745000>
>>     at org.junit.Assert.fail(Assert.java:88)
>>     at org.junit.Assert.failNotEquals(Assert.java:834)
>>     at org.junit.Assert.assertEquals(Assert.java:645)
>>     at org.junit.Assert.assertEquals(Assert.java:631)
>>     at
>>
>> test.general.ISO8601DateParserTest.testDateParsing(ISO8601DateParserTest.java:45)
>>
>> I'm guessing this is some kind of timezone error since my laptop is on PDT
>> and the timestamp is exactly 3 hours off ...
>>
>>
>> On Tue, Jul 12, 2016 at 9:05 AM, Ellison Anne Williams <
>> [email protected]> wrote:
>>
>> > Hi Tim,
>> >
>> > It's building fine for us here and the unit tests are passing (a couple
>> of
>> > us just tried a fresh pull and build) . There are 23 unit tests and a
>> > distributed test framework (that's meant to run on a live cluster) that
>> is
>> > far more extensive.
>> >
>> > What are the errors that you are receiving? Happy to help troubleshoot
>> the
>> > issues.
>> >
>> > Thanks!
>> >
>> > Ellison Anne
>> >
>> > On Tue, Jul 12, 2016 at 11:56 AM, Tim Ellison <[email protected]>
>> > wrote:
>> >
>> > > I was able to clone the code from Github, and compile it!
>> > >
>> > > I know folks are busy getting the project set-up, just wanted to check
>> > > that (i) all the unit tests you expected to be there are committed
>> > > (there are not many), and (ii) that you expect the tests to pass (they
>> > > don't for me).
>> > >
>> > > Regards,
>> > > Tim
>> > >
>> > > On 12/07/16 14:47, Ellison Anne Williams wrote:
>> > > > Thanks Josh - I made a trivial commit and it seemed to trigger.
>> > > >
>> > > > On Mon, Jul 11, 2016 at 11:00 PM, Josh Elser <[email protected]>
>> > > wrote:
>> > > >
>> > > >> Sometimes it gets "stuck" (I don't think I ever got a more specific
>> > > answer
>> > > >> from infra on "why"). You can try to just make some
>> > > >> trivial/whitespace/empty commit to try to force it to run the
>> mirror
>> > > steps
>> > > >> again.
>> > > >>
>> > > >>
>> > > >> Joe Witt wrote:
>> > > >>
>> > > >>> It can take seconds to hours but usually is fast.
>> > > >>> On Jul 11, 2016 7:41 PM, "Ellison Anne Williams"<
>> > > [email protected]
>> > > >>>>
>> > > >>> wrote:
>> > > >>>
>> > > >>> Hi,
>> > > >>>>
>> > > >>>> How long does it take for the code to mirror from
>> > > >>>> https://git-wip-us.apache.org/repos/asf/incubator-pirk.git over
>> to
>> > > >>>> Github
>> > > >>>> (
>> > > >>>> https://github.com/apache/incubator-pirk)? I am assuming that
>> it's
>> > > >>>> automatic, but I am not seeing it reflected after about 45
>> minutes
>> > and
>> > > >>>> just
>> > > >>>> wanted to check to see if I was supposed to do something else
>> > > manually...
>> > > >>>>
>> > > >>>> Thanks!
>> > > >>>>
>> > > >>>> Ellison Anne
>> > > >>>>
>> > > >>>>
>> > > >>>
>> > > >
>> > >
>> >
>>
>
>

Reply via email to