Travis CI using xenial for python 3.5

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Travis CI using xenial for python 3.5

Nick Hall
Devs,

As part of PR #789 I was going to bump the minimum python version to 3.5
and decided to upgrade Travis CI to use xenial.

https://github.com/gramps-project/gramps/pull/789

There were two problems:

1. Ubuntu xenial doesn't have the python3-pyicu package, but we don't
need it in the unit tests.

2. We are getting the following error:

     Failed to connect to Mir: Failed to connect to server socket: No
such file or directory
     Unable to init server: Could not connect: Connection refused

I attempted to fix it by setting the DISPLAY environment variable, but
had no luck.

As a result I have decided to bump the minimum python version to 3.3 as
previously suggested.

However, since we may want to move to xenial in the future, I thought I
would mention these two problems.  The build still passes, but does
anyone know of a fix?  Can python3-pyicu be loaded using pip in Travis?

Regards,


Nick.



_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: Travis CI using xenial for python 3.5

John Ralls-2


> On May 13, 2019, at 10:15 AM, Nick Hall <[hidden email]> wrote:
>
> Devs,
>
> As part of PR #789 I was going to bump the minimum python version to 3.5 and decided to upgrade Travis CI to use xenial.
>
> https://github.com/gramps-project/gramps/pull/789
>
> There were two problems:
>
> 1. Ubuntu xenial doesn't have the python3-pyicu package, but we don't need it in the unit tests.
>
> 2. We are getting the following error:
>
>     Failed to connect to Mir: Failed to connect to server socket: No such file or directory
>     Unable to init server: Could not connect: Connection refused
>
> I attempted to fix it by setting the DISPLAY environment variable, but had no luck.
>
> As a result I have decided to bump the minimum python version to 3.3 as previously suggested.
>
> However, since we may want to move to xenial in the future, I thought I would mention these two problems.  The build still passes, but does anyone know of a fix?  Can python3-pyicu be loaded using pip in Travis?
>

Hmm, you're not supposed to be able to run any GUI inside a docker, you connect to the GUI on the outside. Christoph Reiter has some advice in this PyGobject issue: https://gitlab.gnome.org/GNOME/pygobject/issues/207

Yes, you should be able to `pip install PyICU`, though it may whine about the ancient version of pip.

Regards,
John Ralls




_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: Travis CI using xenial for python 3.5

Nick Hall
On 13/05/2019 23:05, John Ralls wrote:
> Hmm, you're not supposed to be able to run any GUI inside a docker, you connect to the GUI on the outside. Christoph Reiter has some advice in this PyGobject issue:https://gitlab.gnome.org/GNOME/pygobject/issues/207

Thanks.  Some of our unit tests must be trying to access the GUI.

When I have time I'll run the tests in verbose mode to see which tests
are causing the errors.

>
> Yes, you should be able to `pip install PyICU`, though it may whine about the ancient version of pip.

That would be very easy to try.

Regards,


Nick.




_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: Travis CI using xenial for python 3.5

Ross Gammon
We shouldn't need to use pip, the python 3 version of icu is in Xenial.

The package is called python3-icu, not python3-pyicu.

Ross

On 14/05/2019 10:26, Nick Hall wrote:

> On 13/05/2019 23:05, John Ralls wrote:
>> Hmm, you're not supposed to be able to run any GUI inside a docker,
>> you connect to the GUI on the outside. Christoph Reiter has some
>> advice in this PyGobject
>> issue:https://gitlab.gnome.org/GNOME/pygobject/issues/207
>
> Thanks.  Some of our unit tests must be trying to access the GUI.
>
> When I have time I'll run the tests in verbose mode to see which tests
> are causing the errors.
>
>>
>> Yes, you should be able to `pip install PyICU`, though it may whine
>> about the ancient version of pip.
>
> That would be very easy to try.
>
> Regards,
>
>
> Nick.
>
>
>
>
> _______________________________________________
> Gramps-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gramps-devel


_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Travis CI using xenial for python 3.5

Nick Hall
On 16/05/2019 19:37, Ross Gammon wrote:
> We shouldn't need to use pip, the python 3 version of icu is in Xenial.
>
> The package is called python3-icu, not python3-pyicu.

Thanks for pointing that out.  The python 2 version is python-pyicu and
the python 3 version is python3-icu.

I'll give it a try.

Nick.




_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel