You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Alex Amato <aj...@google.com> on 2019/01/30 21:33:14 UTC

Re: [BEAM-6551] Python precommit is broken due to pyLint issues

(Renaming subject and updating jira to reflect pyLint issue.)

Unfortunately it occurred again when I reran the python precommit.

https://jira.apache.org/jira/browse/BEAM-6551?filter=-2

04:58:37 > Task :beam-sdks-python:lintPy27 FAILED

https://builds.apache.org/job/beam_PreCommit_Python_Commit/3984/console

https://builds.apache.org/job/beam_PreCommit_Python_Commit/3984/


On Wed, Jan 30, 2019 at 11:01 AM Michael Luckey <mi...@gmail.com>
wrote:

> Lucky u.
>
> I have always to exclude python run from my Gradle builds locally… seems
> to work reliable only, if not run in parallel :(
>
> I always thought there is some parallelity issue - possibly on the virtual
> envs… But as precommit is doing well on Jenkins…
>
> Never had the time to look into the setup, though….
>
>
> On 30. Jan 2019, at 19:48, Alex Amato <aj...@google.com> wrote:
>
> I'm just doing to re run the precommit and see if it happens again. I
> can't find the error why it failed, and it won't fail when I run locally...
>
> On Wed, Jan 30, 2019 at 10:08 AM Michael Luckey <ad...@gmail.com>
> wrote:
>
>> There is (probably?):
>>
>> *04:58:37* >* Task :beam-sdks-python:lintPy27* FAILED
>>
>>
>> Dunno if more is failing....
>>
>>
>>
>> On Wed, Jan 30, 2019 at 6:51 PM Alex Amato <aj...@google.com> wrote:
>>
>>> Ah, my mistake. then I suppose I could not locate the failure in my
>>> build output. There should be some magic "failure" keyword or something,
>>> but I really don't know what it is. Plus the build scan says no failures
>>>
>>> On Wed, Jan 30, 2019 at 9:45 AM Michael Luckey <ad...@gmail.com>
>>> wrote:
>>>
>>>> Don't think, this is failing the build...
>>>>
>>>> E.g. here ( https://scans.gradle.com/s/qxtrr65etbcem/console-log#L4674
>>>> ) we seem to have the same trace on successful build?
>>>>
>>>> On Wed, Jan 30, 2019 at 6:30 PM Alex Amato <aj...@google.com> wrote:
>>>>
>>>>> JIRA link:
>>>>> https://jira.apache.org/jira/browse/BEAM-6551?filter=-2
>>>>>
>>>>>
>>>>> (apache_beam.runners.portability.portable_runner_test.PortableRunnerTestWithExternalEnv)
>>>>>
>>>>> Noticed this one one of my Java PRs:
>>>>> https://builds.apache.org/job/beam_PreCommit_Python_Commit/3984/console
>>>>>
>>>>> https://builds.apache.org/job/beam_PreCommit_Python_Commit/3984/
>>>>>
>>>>>
>>>>> 20:45:52 test_combine_per_key
>>>>> (apache_beam.runners.portability.portable_runner_test.PortableRunnerTestWithExternalEnv)
>>>>> ... E0130 04:45:52.286249311 32115 uri_parser.cc:46] bad uri.scheme:
>>>>> 'localhost'
>>>>> 20:45:52 E0130 04:45:52.286313006 32115 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.286318482 32115 http_proxy.cc:58] cannot
>>>>> parse value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.295928556 32115 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.295985211 32115 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.295990162 32115 http_proxy.cc:58] cannot
>>>>> parse value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.330903987 2223 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.330947684 2223 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.330952104 2223 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.334446074 2230 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.334486801 2230 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.334491220 2230 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.354265388 2240 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.354317198 2240 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.354322290 2240 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.358875721 2240 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.358919350 2240 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.358924715 2240 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 ok
>>>>> 20:45:52 test_create
>>>>> (apache_beam.runners.portability.portable_runner_test.PortableRunnerTestWithExternalEnv)
>>>>> ... E0130 04:45:52.681886813 32115 uri_parser.cc:46] bad uri.scheme:
>>>>> 'localhost'
>>>>> 20:45:52 E0130 04:45:52.681938773 32115 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.681943673 32115 http_proxy.cc:58] cannot
>>>>> parse value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.693522097 32115 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.693571435 32115 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.693576094 32115 http_proxy.cc:58] cannot
>>>>> parse value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.724072136 2270 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.724112120 2270 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.724116587 2270 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.727464086 2276 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.727521232 2276 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.727526422 2276 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.745105061 2286 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.745148909 2286 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.745153757 2286 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 20:45:52 E0130 04:45:52.751653312 2286 uri_parser.cc:46] bad
>>>>> uri.scheme: 'localhost'
>>>>> 20:45:52 E0130 04:45:52.751698315 2286 uri_parser.cc:52] ^ here
>>>>> 20:45:52 E0130 04:45:52.751702859 2286 http_proxy.cc:58] cannot parse
>>>>> value of 'http_proxy' env var
>>>>> 2
>>>>>
>>>>
>