spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Blue <rb...@netflix.com.INVALID>
Subject Re: UnknownTimeZoneError: 'US/Pacific-New'
Date Mon, 08 Apr 2019 17:55:11 GMT
Thanks for the update, Shane!

Is this affecting all PRs or just some unlucky ones? I seem to hit it every
time.

On Mon, Apr 8, 2019 at 10:53 AM shane knapp <sknapp@berkeley.edu> wrote:

> for some background, i noticed this last week right before i was out of
> the office for some personal/medical stuff...  and i have absolutely no
> idea why this is happening.  :(
>
> my PR to move to python3.6 has nothing to do w/this issue.
>
> the real link to track this issue is here:
> https://issues.apache.org/jira/browse/SPARK-27389
>
> i will be investigating this today once i get caught up from last week.
>
>
> On Mon, Apr 8, 2019 at 9:45 AM Ryan Blue <rblue@netflix.com.invalid>
> wrote:
>
>> Any idea when this is going to be fixed?
>>
>> The DataSourceV2 PRs are consistently blocked by this.
>>
>> On Thu, Apr 4, 2019 at 8:19 PM Xiao Li <lixiao@databricks.com> wrote:
>>
>>> I saw multiple PRs are hitting this error:
>>>
>>>   File "/home/anaconda/lib/python2.7/site-packages/pytz/__init__.py", line 178,
in timezone
>>>     raise UnknownTimeZoneError(zone)
>>> UnknownTimeZoneError: 'US/Pacific-New'
>>>
>>> If you hit the same error, it is highly possible that this is not caused
>>> by the code changes in your PR. Please re-trigger the tests.
>>>
>>> For more information, please follow the PR:
>>> https://github.com/apache/spark/pull/24266
>>>
>>> Thanks,
>>>
>>> Xiao
>>>
>>> --
>>> [image:
>>> https://databricks.com/sparkaisummit/north-america?utm_source=email&utm_medium=signature]
>>>
>>>
>>
>> --
>> Ryan Blue
>> Software Engineer
>> Netflix
>>
>
>
> --
> Shane Knapp
> UC Berkeley EECS Research / RISELab Staff Technical Lead
> https://rise.cs.berkeley.edu
>


-- 
Ryan Blue
Software Engineer
Netflix

Mime
View raw message