Hi Richard,
Thanks for the well crafted explanation, and after talking to Paul I got a
clearer picture on which direction we should be heading and we should align
and work towards python3. Maybe I was not aware, my bad.
Cheers,
Aaron
-Original Message-
From: richard.pur...@linuxfoundati
On Wed, 2018-07-11 at 02:23 +, Chan, Aaron Chun Yew wrote:
> It appears that your using virtualenv (switch to python3) to startup
> your buildbot processes and not using the default python from host
> distribution.
> I am aware that you can switch interpreter to python2/3 in
> virtualenv. Shoul
Hi Richard,
It appears that your using virtualenv (switch to python3) to startup your
buildbot processes and not using the default python from host distribution.
I am aware that you can switch interpreter to python2/3 in virtualenv.
Shouldn’t we handle these for both in events users uses
the def
On Tue, 2018-07-10 at 10:47 +, Chan, Aaron Chun Yew wrote:
> [Richard] I think this means you're using python2 and we really
> should be using
> python3 as I don't want to support both...
>
> [Reply] This error/bug was found during buildbot startup meaning this
> is out of my c
Hi Richard,
[Richard] I think this means you're using python2 and we really should be using
python3 as I don't want to support both...
[Reply] This error/bug was found during buildbot startup meaning this is out of
my control.
Maybe you have a fix for this, otherwise
On Tue, 2018-07-10 at 11:24 +0800, Aaron Chan wrote:
> This patch is to fix the inconsistency in loading custom module
> yoctoabb & yocto_console_view during Buildbot Master startup.
>
> Signed-off-by: Aaron Chan
> ---
> __init__.py| 0
> yocto_console_view/__init__.py | 0
>
This patch is to fix the inconsistency in loading custom module
yoctoabb & yocto_console_view during Buildbot Master startup.
Signed-off-by: Aaron Chan
---
__init__.py| 0
yocto_console_view/__init__.py | 0
2 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644
