Hi -
> On Apr 1, 2019, at 10:54 AM, Marcelo Vanzin
> wrote:
>
> On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung wrote:
>> I switched to another environment, found out I needed to manually pip
>> install configparser just to build (skipTest)
>
> There are probably things that could be better d
On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung wrote:
> I switched to another environment, found out I needed to manually pip
> install configparser just to build (skipTest)
There are probably things that could be better documented. Or maybe
could be handled better by the build scripts. But thes
I’m happy to give +1 (binding)
But definitely ran into more problems with this and more time than I
anticipated.
checked:
- name includes incubating
- DISCLAIMER exists
Signature and hashes
- LICENSE and NOTICE all good
Copyright year, url to and copy full text for license
- No unexpected binary
+1 (binding)
And thanks Marcelo for resolving the issues raised on rc1.
On Fri, Mar 29, 2019 at 19:13 Justin Mclean
wrote:
> Hi,
>
> +1 (binding)
>
> Released software can have bugs and failing tests, the only requirement
> from an ASF release point of view is that it can compile. Of course teh
Hi,
+1 (binding)
Released software can have bugs and failing tests, the only requirement from an
ASF release point of view is that it can compile. Of course teh project may
decided not to release it if the bug is serious.
I checked:
- incubating in name
- signatures and hashes correct
- DISCLA
On Thu, Mar 28, 2019 at 3:57 PM Felix Cheung wrote:
> I have LANG=“en_US.UTF-8”
> I tried a couple of things finally it passed when I use virtualenv - my
> python is Python 3, forcing that to Python 2 passed the test.
Hmmm, that tells me that the python 3 path in the fake shell might not be
as
I have LANG=“en_US.UTF-8”
I tried a couple of things finally it passed when I use virtualenv - my
python is Python 3, forcing that to Python 2 passed the test. However, now
another test failed (maybe connection blocked by firewall?)
=== FAILURES
===
I can reproduce it with this:
LC_ALL=en_US.ASCII mvn -Pspark-2.4 -Pthriftserver test -pl :livy-repl_2.11
-Dsuites=*.Python2*
Seems that Livy's fake python shell expects UTF-8 when running on Python 2.
This is not a new bug, so while we should fix it, not sure we need to fix
it in this release.
On Thu, 28 Mar 2019 at 17:02, Marcelo Vanzin
wrote:
> Are you using a different encoding that UTF-8 in your environment?
>
> The source file contains unicode escapes, so that shouldn't be the problem.
> It may be the test is expecting the output of child processes (in this case
> the python inter
Also is that failing when running the Python2 or the Python3 version of
that test? Maybe it doesn't work as expected in some newer version of
Python3...
On Thu, Mar 28, 2019 at 10:02 AM Marcelo Vanzin wrote:
> Are you using a different encoding that UTF-8 in your environment?
>
> The source file
Are you using a different encoding that UTF-8 in your environment?
The source file contains unicode escapes, so that shouldn't be the problem.
It may be the test is expecting the output of child processes (in this case
the python interpreter) to be UTF-8.
On Wed, Mar 27, 2019 at 10:25 PM Felix Ch
On Thu, 28 Mar 2019 at 15:42, Felix Cheung wrote:
> I see, thanks. Perhaps the way I unzip the src zip file then. Is it a
> better approach to unpack it?
>
>
Have a look at the test file source to see if it looks OK.
>
> On Thu, Mar 28, 2019 at 2:03 AM sebb wrote:
>
> > On Thu, 28 Mar 2019 at
I see, thanks. Perhaps the way I unzip the src zip file then. Is it a
better approach to unpack it?
On Thu, Mar 28, 2019 at 2:03 AM sebb wrote:
> On Thu, 28 Mar 2019 at 05:25, Felix Cheung wrote:
>
> > This test is consistently failing when I build, any idea what’s wrong in
> my
> > setup?
> >
On Thu, 28 Mar 2019 at 05:25, Felix Cheung wrote:
> This test is consistently failing when I build, any idea what’s wrong in my
> setup?
>
> - should print unicode correctly *** FAILED *** (101 milliseconds)
> ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
> ExecuteSuccess
This test is consistently failing when I build, any idea what’s wrong in my
setup?
- should print unicode correctly *** FAILED *** (101 milliseconds)
ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
ExecuteSuccess(JObject(List((text/plain,JString(☺)
(PythonInterpreterSpec
The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy release.
Livy enables programmatic, fault-tolerant, multi-tenant submission of
Spark jobs from web/mobile apps (no Spark client needed). So, multiple
users can interact with your Spark cluster concurrently and reliably.
Vote threa
16 matches
Mail list logo
