Oh, I just missed it then :) Thank you Lukasz for connecting us. Yeah, the two TimerReceiverTest tests fail reliably for me.
On Tue, 2 Apr 2019 at 23:53, Lukasz Cwik <[email protected]> wrote: > +Ahmed > > I have added you as a contributor. > > It seems as though Ahmed had just picked up BEAM-3489 yesterday. Reach out > to Ahmed if you would like to help them out with the task. > > Was TimerReceiverTest failing reliably when performing a parallel build or > is it flaky? > > I have asked Chamikara to take a look for PR 8180. > > > On Tue, Apr 2, 2019 at 8:33 AM Csaba Kassai <[email protected]> wrote: > >> Hi All! >> >> I am Csabi, I would be happy to contribute to Beam. >> Could you grant me contributor role and assign issue BEAM-3489 >> <https://issues.apache.org/jira/browse/BEAM-3489> to me? My user name >> is "csabakassai". >> >> After I checked out the code and tried to do a gradle check I found these >> issues: >> >> 1. *jUnit tests fails:* the TimerReceiverTest fails in the >> ":beam-runners-google-cloud-dataflow-java-fn-api-worker:test" and the >> ":beam-runners-google-cloud-dataflow-java-legacy-worker:test" tasks. When >> I >> execute tests independently everything is fine, so I disabled the parallel >> build and this solves the problem. I have not investigated further, do you >> have any more insights on this issue? I have attached the test reports. >> 2. *python test fail*: there is a python test which fails if the >> current offset of your timezone differs from the offset in 1970. In my >> case >> the Singapore is now GMT+8 and it was GMT+7:30 in 1970. I created a ticket >> for this issue where I I describe the problem in details: >> https://jira.apache.org/jira/browse/BEAM-6947. Could you assign the >> ticket to me? Also I created a PR with a possible fix: >> https://github.com/apache/beam/pull/8180. Could you suggest me a >> reviewer? >> >> >> Thank you, >> Csabi >> >> >> >>
