Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Murtuza Zabuawala 
Yes that I understood.

I was targeting Python2.6 in general and by the way on 2020 we'll also have
EOL for Python2.7 ;-)

On Mon, Sep 11, 2017 at 3:29 PM, Dave Page  wrote:

> Well this is only for the CI of course - and we could limit it to just
> Python 2.6.
>
> Plus... the wheel package is only used for creating the wheel, which is
> done on 2.7 anyway.
>
> On Mon, Sep 11, 2017 at 10:43 AM, Murtuza Zabuawala  enterprisedb.com> wrote:
>
>> That will work but If we stick with older versions then we won't be able
>> to take advantages of bug fixes, security related fixes etc until CentOS6
>> is dead(which is 30 Nov 2020 EOL), I personally don't think that's a good
>> idea.
>>
>> On Mon, Sep 11, 2017 at 3:01 PM, Dave Page  wrote:
>>
>>> Hi
>>>
>>> On Mon, Sep 11, 2017 at 10:27 AM, Murtuza Zabuawala <
>>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>>
 This is what I have in my system, which is working fine

 (venv26) murtuza@ubuntu-vm:[~/projects/pgadmin4/web/regression]$ python
 Python 2.6.9 (default, Mar  6 2016, 02:31:36)
 [GCC 5.3.1 20160225] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import wheel
 >>> wheel.__version__
 '0.30.0.a0'


 Can you check on the build machine if it is newer version which is
 0.30.0?

 -__version__ = "0.30.0a0"
 +__version__ = "0.30.0"

>>>
>>> Not sure how that can work - the release notes for 0.30.0 specifically
>>> say:
>>>
>>>
>>>- Removed support for Python 2.6, 3.2 and 3.3.
>>>
>>> I'm thinking the attached patch is the way to go for Jenkins. Thoughts?
>>>
>>>

 Ref: Link
 

 --
 Regards,
 Murtuza Zabuawala
 EnterpriseDB: http://www.enterprisedb.com
 The Enterprise PostgreSQL Company

 [image: https://community.postgresrocks.net/]
 

 On Mon, Sep 11, 2017 at 2:52 PM, Murtuza Zabuawala <
 murtuza.zabuaw...@enterprisedb.com> wrote:

> It's newer version of wheel is breaking this, set literals are not
> implemented in Python2.6.
>
> Unsupported syntax for Python2.6: { 'PKG-INFO', 'requires.txt',
> 'SOURCES.txt', }
>
> They released newer version couple of hours before :(
>
>
> On Mon, Sep 11, 2017 at 2:32 PM, Dave Page  wrote:
>
>> Please also check the python wheel builds OK - iirc, packages with
>> conditionals in them in requirements.txt need special handling in 
>> setup.py.
>>
>> On Mon, Sep 11, 2017 at 9:55 AM, Dave Page  wrote:
>>
>>> Great, but what's breaking Jenkins?
>>>
>>> On Mon, Sep 11, 2017 at 9:54 AM, Murtuza Zabuawala <
>>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>>
 I'm able to run tests & pgAdmin4 on my machine using Python2.6.

 --
 Regards,
 Murtuza Zabuawala
 EnterpriseDB: http://www.enterprisedb.com
 The Enterprise PostgreSQL Company

 [image: https://community.postgresrocks.net/]
 

 On Mon, Sep 11, 2017 at 2:08 PM, Dave Page 
 wrote:

> Murtuza, please look into this ASAP. I need the builds to go green
> so I can cut the release!
>
> On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins <
> jenk...@pgadmin.org> wrote:
>
>> See > 6/display/redirect?page=changes>
>>
>> Changes:
>>
>> [Dave Page] Stick with the older Flask-Script module for Python
>> 2.6
>>
>> --
>> Started by an SCM change
>> Started by an SCM change
>> Started by an SCM change
>> Started by an SCM change
>> Started by an SCM change
>> [EnvInject] - Loading node environment variables.
>> Building in workspace > ob/pgadmin4-master-python26/ws/>
>>  > git rev-parse --is-inside-work-tree # timeout=10
>> Fetching changes from the remote Git repository
>>  > git config remote.origin.url git://git.postgresql.org/git/p
>> gadmin4.git # timeout=10
>> Cleaning workspace
>>  > git rev-parse --verify HEAD # timeout=10
>> Resetting working tree
>>  > git reset --hard # timeout=10
>>  > git clean -fdx # timeout=10
>> Fetching upstream changes from git://git.postgresql.org/git/p
>> gadmin4.git
>>  > git --version # timeout=10
>>  > git fetch --tags --progress git://git.postgresql.org/git/p
>>

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Murtuza Zabuawala 
That will work but If we stick with older versions then we won't be able to
take advantages of bug fixes, security related fixes etc until CentOS6 is
dead(which is 30 Nov 2020 EOL), I personally don't think that's a good idea.

On Mon, Sep 11, 2017 at 3:01 PM, Dave Page  wrote:

> Hi
>
> On Mon, Sep 11, 2017 at 10:27 AM, Murtuza Zabuawala  enterprisedb.com> wrote:
>
>> This is what I have in my system, which is working fine
>>
>> (venv26) murtuza@ubuntu-vm:[~/projects/pgadmin4/web/regression]$ python
>> Python 2.6.9 (default, Mar  6 2016, 02:31:36)
>> [GCC 5.3.1 20160225] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import wheel
>> >>> wheel.__version__
>> '0.30.0.a0'
>>
>>
>> Can you check on the build machine if it is newer version which is 0.30.0?
>>
>> -__version__ = "0.30.0a0"
>> +__version__ = "0.30.0"
>>
>
> Not sure how that can work - the release notes for 0.30.0 specifically say:
>
>
>- Removed support for Python 2.6, 3.2 and 3.3.
>
> I'm thinking the attached patch is the way to go for Jenkins. Thoughts?
>
>
>>
>> Ref: Link
>> 
>>
>> --
>> Regards,
>> Murtuza Zabuawala
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>> [image: https://community.postgresrocks.net/]
>> 
>>
>> On Mon, Sep 11, 2017 at 2:52 PM, Murtuza Zabuawala <
>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>
>>> It's newer version of wheel is breaking this, set literals are not
>>> implemented in Python2.6.
>>>
>>> Unsupported syntax for Python2.6: { 'PKG-INFO', 'requires.txt',
>>> 'SOURCES.txt', }
>>>
>>> They released newer version couple of hours before :(
>>>
>>>
>>> On Mon, Sep 11, 2017 at 2:32 PM, Dave Page  wrote:
>>>
 Please also check the python wheel builds OK - iirc, packages with
 conditionals in them in requirements.txt need special handling in setup.py.

 On Mon, Sep 11, 2017 at 9:55 AM, Dave Page  wrote:

> Great, but what's breaking Jenkins?
>
> On Mon, Sep 11, 2017 at 9:54 AM, Murtuza Zabuawala <
> murtuza.zabuaw...@enterprisedb.com> wrote:
>
>> I'm able to run tests & pgAdmin4 on my machine using Python2.6.
>>
>> --
>> Regards,
>> Murtuza Zabuawala
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>> [image: https://community.postgresrocks.net/]
>> 
>>
>> On Mon, Sep 11, 2017 at 2:08 PM, Dave Page  wrote:
>>
>>> Murtuza, please look into this ASAP. I need the builds to go green
>>> so I can cut the release!
>>>
>>> On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins <
>>> jenk...@pgadmin.org> wrote:
>>>
 See 

 Changes:

 [Dave Page] Stick with the older Flask-Script module for Python 2.6

 --
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 [EnvInject] - Loading node environment variables.
 Building in workspace 
  > git rev-parse --is-inside-work-tree # timeout=10
 Fetching changes from the remote Git repository
  > git config remote.origin.url git://git.postgresql.org/git/p
 gadmin4.git # timeout=10
 Cleaning workspace
  > git rev-parse --verify HEAD # timeout=10
 Resetting working tree
  > git reset --hard # timeout=10
  > git clean -fdx # timeout=10
 Fetching upstream changes from git://git.postgresql.org/git/p
 gadmin4.git
  > git --version # timeout=10
  > git fetch --tags --progress git://git.postgresql.org/git/p
 gadmin4.git +refs/heads/*:refs/remotes/origin/*
  > git rev-parse origin/master^{commit} # timeout=10
 Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
 (origin/master)
 Commit message: "Stick with the older Flask-Script module for
 Python 2.6"
  > git config core.sparsecheckout # timeout=10
  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 #
 timeout=10
 [EnvInject] - Executing scripts and injecting environment variables
 after the SCM step.
 [EnvInject] - Injecting as environment variables the properties
 content
 PYTHON_VERSION=2.6

 [EnvInject] -

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Dave Page 
Hi

On Mon, Sep 11, 2017 at 10:27 AM, Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:

> This is what I have in my system, which is working fine
>
> (venv26) murtuza@ubuntu-vm:[~/projects/pgadmin4/web/regression]$ python
> Python 2.6.9 (default, Mar  6 2016, 02:31:36)
> [GCC 5.3.1 20160225] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import wheel
> >>> wheel.__version__
> '0.30.0.a0'
>
>
> Can you check on the build machine if it is newer version which is 0.30.0?
>
> -__version__ = "0.30.0a0"
> +__version__ = "0.30.0"
>

Not sure how that can work - the release notes for 0.30.0 specifically say:


   - Removed support for Python 2.6, 3.2 and 3.3.

I'm thinking the attached patch is the way to go for Jenkins. Thoughts?


>
> Ref: Link
> 
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> [image: https://community.postgresrocks.net/]
> 
>
> On Mon, Sep 11, 2017 at 2:52 PM, Murtuza Zabuawala  enterprisedb.com> wrote:
>
>> It's newer version of wheel is breaking this, set literals are not
>> implemented in Python2.6.
>>
>> Unsupported syntax for Python2.6: { 'PKG-INFO', 'requires.txt',
>> 'SOURCES.txt', }
>>
>> They released newer version couple of hours before :(
>>
>>
>> On Mon, Sep 11, 2017 at 2:32 PM, Dave Page  wrote:
>>
>>> Please also check the python wheel builds OK - iirc, packages with
>>> conditionals in them in requirements.txt need special handling in setup.py.
>>>
>>> On Mon, Sep 11, 2017 at 9:55 AM, Dave Page  wrote:
>>>
 Great, but what's breaking Jenkins?

 On Mon, Sep 11, 2017 at 9:54 AM, Murtuza Zabuawala <
 murtuza.zabuaw...@enterprisedb.com> wrote:

> I'm able to run tests & pgAdmin4 on my machine using Python2.6.
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> [image: https://community.postgresrocks.net/]
> 
>
> On Mon, Sep 11, 2017 at 2:08 PM, Dave Page  wrote:
>
>> Murtuza, please look into this ASAP. I need the builds to go green so
>> I can cut the release!
>>
>> On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins <
>> jenk...@pgadmin.org> wrote:
>>
>>> See >> 6/display/redirect?page=changes>
>>>
>>> Changes:
>>>
>>> [Dave Page] Stick with the older Flask-Script module for Python 2.6
>>>
>>> --
>>> Started by an SCM change
>>> Started by an SCM change
>>> Started by an SCM change
>>> Started by an SCM change
>>> Started by an SCM change
>>> [EnvInject] - Loading node environment variables.
>>> Building in workspace >> ob/pgadmin4-master-python26/ws/>
>>>  > git rev-parse --is-inside-work-tree # timeout=10
>>> Fetching changes from the remote Git repository
>>>  > git config remote.origin.url git://git.postgresql.org/git/p
>>> gadmin4.git # timeout=10
>>> Cleaning workspace
>>>  > git rev-parse --verify HEAD # timeout=10
>>> Resetting working tree
>>>  > git reset --hard # timeout=10
>>>  > git clean -fdx # timeout=10
>>> Fetching upstream changes from git://git.postgresql.org/git/p
>>> gadmin4.git
>>>  > git --version # timeout=10
>>>  > git fetch --tags --progress git://git.postgresql.org/git/p
>>> gadmin4.git +refs/heads/*:refs/remotes/origin/*
>>>  > git rev-parse origin/master^{commit} # timeout=10
>>> Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>>> (origin/master)
>>> Commit message: "Stick with the older Flask-Script module for Python
>>> 2.6"
>>>  > git config core.sparsecheckout # timeout=10
>>>  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>>>  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 #
>>> timeout=10
>>> [EnvInject] - Executing scripts and injecting environment variables
>>> after the SCM step.
>>> [EnvInject] - Injecting as environment variables the properties
>>> content
>>> PYTHON_VERSION=2.6
>>>
>>> [EnvInject] - Variables injected successfully.
>>> [pgadmin4-master-python26] $ /bin/sh -xe
>>> /tmp/jenkins1541475390173008577.sh
>>> + >> /ci/ci_runner.sh>
>>> EXECUTING: Create pgAdmin config
>>>
>>> EXECUTING: Python tests
>>>
>>> Creating Python 2.6 virtual environment...
>>>
>>> New python executable in

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Murtuza Zabuawala 
It's newer version of wheel is breaking this, set literals are not
implemented in Python2.6.

Unsupported syntax for Python2.6: { 'PKG-INFO', 'requires.txt',
'SOURCES.txt', }

They released newer version couple of hours before :(


On Mon, Sep 11, 2017 at 2:32 PM, Dave Page  wrote:

> Please also check the python wheel builds OK - iirc, packages with
> conditionals in them in requirements.txt need special handling in setup.py.
>
> On Mon, Sep 11, 2017 at 9:55 AM, Dave Page  wrote:
>
>> Great, but what's breaking Jenkins?
>>
>> On Mon, Sep 11, 2017 at 9:54 AM, Murtuza Zabuawala <
>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>
>>> I'm able to run tests & pgAdmin4 on my machine using Python2.6.
>>>
>>> --
>>> Regards,
>>> Murtuza Zabuawala
>>> EnterpriseDB: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>> [image: https://community.postgresrocks.net/]
>>> 
>>>
>>> On Mon, Sep 11, 2017 at 2:08 PM, Dave Page  wrote:
>>>
 Murtuza, please look into this ASAP. I need the builds to go green so I
 can cut the release!

 On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins  wrote:

> See  6/display/redirect?page=changes>
>
> Changes:
>
> [Dave Page] Stick with the older Flask-Script module for Python 2.6
>
> --
> Started by an SCM change
> Started by an SCM change
> Started by an SCM change
> Started by an SCM change
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building in workspace  ob/pgadmin4-master-python26/ws/>
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url git://git.postgresql.org/git/p
> gadmin4.git # timeout=10
> Cleaning workspace
>  > git rev-parse --verify HEAD # timeout=10
> Resetting working tree
>  > git reset --hard # timeout=10
>  > git clean -fdx # timeout=10
> Fetching upstream changes from git://git.postgresql.org/git/p
> gadmin4.git
>  > git --version # timeout=10
>  > git fetch --tags --progress git://git.postgresql.org/git/p
> gadmin4.git +refs/heads/*:refs/remotes/origin/*
>  > git rev-parse origin/master^{commit} # timeout=10
> Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
> (origin/master)
> Commit message: "Stick with the older Flask-Script module for Python
> 2.6"
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 # timeout=10
> [EnvInject] - Executing scripts and injecting environment variables
> after the SCM step.
> [EnvInject] - Injecting as environment variables the properties content
> PYTHON_VERSION=2.6
>
> [EnvInject] - Variables injected successfully.
> [pgadmin4-master-python26] $ /bin/sh -xe /tmp/jenkins154147539017300857
> 7.sh
> +  /ci/ci_runner.sh>
> EXECUTING: Create pgAdmin config
>
> EXECUTING: Python tests
>
> Creating Python 2.6 virtual environment...
>
> New python executable in  ob/pgadmin4-master-python26/ws/pgadmin-venv/bin/python>
> Installing setuptools, pip, wheel...done.
> Running virtualenv with interpreter /usr/local/python-2.6/bin/python
> DEPRECATION: Python 2.6 is no longer supported by the Python core
> team, please upgrade your Python. A future version of pip will drop 
> support
> for Python 2.6
> Collecting Babel==2.3.4 (from -r requirements.txt (line 4))
>   Using cached Babel-2.3.4-py2.py3-none-any.whl
> Collecting beautifulsoup4==4.4.1 (from -r requirements.txt (line 5))
>   Using cached beautifulsoup4-4.4.1-py2-none-any.whl
> Collecting blinker==1.3 (from -r requirements.txt (line 6))
> Collecting click==6.6 (from -r requirements.txt (line 7))
>   Using cached click-6.6-py2.py3-none-any.whl
> Collecting extras==0.0.3 (from -r requirements.txt (line 8))
> Collecting fixtures==2.0.0 (from -r requirements.txt (line 9))
>   Using cached fixtures-2.0.0-py2.py3-none-any.whl
> Collecting Flask==0.11.1 (from -r requirements.txt (line 10))
>   Using cached Flask-0.11.1-py2.py3-none-any.whl
> Collecting Flask-Babel==0.11.1 (from -r requirements.txt (line 11))
> Collecting Flask-Gravatar==0.4.2 (from -r requirements.txt (line 12))
>   Using cached Flask_Gravatar-0.4.2-py2.py3-none-any.whl
> Collecting Flask-HTMLmin==1.2 (from -r requirements.txt (line 13))
> Collecting Flask-Login==0.3.2 (from -r

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Dave Page 
Please also check the python wheel builds OK - iirc, packages with
conditionals in them in requirements.txt need special handling in setup.py.

On Mon, Sep 11, 2017 at 9:55 AM, Dave Page  wrote:

> Great, but what's breaking Jenkins?
>
> On Mon, Sep 11, 2017 at 9:54 AM, Murtuza Zabuawala  enterprisedb.com> wrote:
>
>> I'm able to run tests & pgAdmin4 on my machine using Python2.6.
>>
>> --
>> Regards,
>> Murtuza Zabuawala
>> EnterpriseDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>> [image: https://community.postgresrocks.net/]
>> 
>>
>> On Mon, Sep 11, 2017 at 2:08 PM, Dave Page  wrote:
>>
>>> Murtuza, please look into this ASAP. I need the builds to go green so I
>>> can cut the release!
>>>
>>> On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins 
>>> wrote:
>>>
 See 

 Changes:

 [Dave Page] Stick with the older Flask-Script module for Python 2.6

 --
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 Started by an SCM change
 [EnvInject] - Loading node environment variables.
 Building in workspace 
  > git rev-parse --is-inside-work-tree # timeout=10
 Fetching changes from the remote Git repository
  > git config remote.origin.url git://git.postgresql.org/git/p
 gadmin4.git # timeout=10
 Cleaning workspace
  > git rev-parse --verify HEAD # timeout=10
 Resetting working tree
  > git reset --hard # timeout=10
  > git clean -fdx # timeout=10
 Fetching upstream changes from git://git.postgresql.org/git/p
 gadmin4.git
  > git --version # timeout=10
  > git fetch --tags --progress git://git.postgresql.org/git/p
 gadmin4.git +refs/heads/*:refs/remotes/origin/*
  > git rev-parse origin/master^{commit} # timeout=10
 Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
 (origin/master)
 Commit message: "Stick with the older Flask-Script module for Python
 2.6"
  > git config core.sparsecheckout # timeout=10
  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 # timeout=10
 [EnvInject] - Executing scripts and injecting environment variables
 after the SCM step.
 [EnvInject] - Injecting as environment variables the properties content
 PYTHON_VERSION=2.6

 [EnvInject] - Variables injected successfully.
 [pgadmin4-master-python26] $ /bin/sh -xe /tmp/jenkins154147539017300857
 7.sh
 + 
 EXECUTING: Create pgAdmin config

 EXECUTING: Python tests

 Creating Python 2.6 virtual environment...

 New python executable in 
 Installing setuptools, pip, wheel...done.
 Running virtualenv with interpreter /usr/local/python-2.6/bin/python
 DEPRECATION: Python 2.6 is no longer supported by the Python core team,
 please upgrade your Python. A future version of pip will drop support for
 Python 2.6
 Collecting Babel==2.3.4 (from -r requirements.txt (line 4))
   Using cached Babel-2.3.4-py2.py3-none-any.whl
 Collecting beautifulsoup4==4.4.1 (from -r requirements.txt (line 5))
   Using cached beautifulsoup4-4.4.1-py2-none-any.whl
 Collecting blinker==1.3 (from -r requirements.txt (line 6))
 Collecting click==6.6 (from -r requirements.txt (line 7))
   Using cached click-6.6-py2.py3-none-any.whl
 Collecting extras==0.0.3 (from -r requirements.txt (line 8))
 Collecting fixtures==2.0.0 (from -r requirements.txt (line 9))
   Using cached fixtures-2.0.0-py2.py3-none-any.whl
 Collecting Flask==0.11.1 (from -r requirements.txt (line 10))
   Using cached Flask-0.11.1-py2.py3-none-any.whl
 Collecting Flask-Babel==0.11.1 (from -r requirements.txt (line 11))
 Collecting Flask-Gravatar==0.4.2 (from -r requirements.txt (line 12))
   Using cached Flask_Gravatar-0.4.2-py2.py3-none-any.whl
 Collecting Flask-HTMLmin==1.2 (from -r requirements.txt (line 13))
 Collecting Flask-Login==0.3.2 (from -r requirements.txt (line 14))
 Collecting Flask-Mail==0.9.1 (from -r requirements.txt (line 15))
 Collecting Flask-Migrate==2.0.3 (from -r requirements.txt (line 16))
 Collecting Flask-Principal==0.4.0 (from -r requirements.txt (line 17))
 Collecting Flask-Security==1.7.5 (from -r requirements.txt (line 18))
 Collecting Flask-SQLAlchemy==2.1 (from -r requirements.txt (line 19))
 Collecting Flask-WTF==0.12

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Dave Page 
Great, but what's breaking Jenkins?

On Mon, Sep 11, 2017 at 9:54 AM, Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:

> I'm able to run tests & pgAdmin4 on my machine using Python2.6.
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> [image: https://community.postgresrocks.net/]
> 
>
> On Mon, Sep 11, 2017 at 2:08 PM, Dave Page  wrote:
>
>> Murtuza, please look into this ASAP. I need the builds to go green so I
>> can cut the release!
>>
>> On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins 
>> wrote:
>>
>>> See >> 6/display/redirect?page=changes>
>>>
>>> Changes:
>>>
>>> [Dave Page] Stick with the older Flask-Script module for Python 2.6
>>>
>>> --
>>> Started by an SCM change
>>> Started by an SCM change
>>> Started by an SCM change
>>> Started by an SCM change
>>> Started by an SCM change
>>> [EnvInject] - Loading node environment variables.
>>> Building in workspace >> ob/pgadmin4-master-python26/ws/>
>>>  > git rev-parse --is-inside-work-tree # timeout=10
>>> Fetching changes from the remote Git repository
>>>  > git config remote.origin.url git://git.postgresql.org/git/p
>>> gadmin4.git # timeout=10
>>> Cleaning workspace
>>>  > git rev-parse --verify HEAD # timeout=10
>>> Resetting working tree
>>>  > git reset --hard # timeout=10
>>>  > git clean -fdx # timeout=10
>>> Fetching upstream changes from git://git.postgresql.org/git/pgadmin4.git
>>>  > git --version # timeout=10
>>>  > git fetch --tags --progress git://git.postgresql.org/git/pgadmin4.git
>>> +refs/heads/*:refs/remotes/origin/*
>>>  > git rev-parse origin/master^{commit} # timeout=10
>>> Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>>> (origin/master)
>>> Commit message: "Stick with the older Flask-Script module for Python 2.6"
>>>  > git config core.sparsecheckout # timeout=10
>>>  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>>>  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 # timeout=10
>>> [EnvInject] - Executing scripts and injecting environment variables
>>> after the SCM step.
>>> [EnvInject] - Injecting as environment variables the properties content
>>> PYTHON_VERSION=2.6
>>>
>>> [EnvInject] - Variables injected successfully.
>>> [pgadmin4-master-python26] $ /bin/sh -xe /tmp/jenkins154147539017300857
>>> 7.sh
>>> + >> /ci/ci_runner.sh>
>>> EXECUTING: Create pgAdmin config
>>>
>>> EXECUTING: Python tests
>>>
>>> Creating Python 2.6 virtual environment...
>>>
>>> New python executable in >> ob/pgadmin4-master-python26/ws/pgadmin-venv/bin/python>
>>> Installing setuptools, pip, wheel...done.
>>> Running virtualenv with interpreter /usr/local/python-2.6/bin/python
>>> DEPRECATION: Python 2.6 is no longer supported by the Python core team,
>>> please upgrade your Python. A future version of pip will drop support for
>>> Python 2.6
>>> Collecting Babel==2.3.4 (from -r requirements.txt (line 4))
>>>   Using cached Babel-2.3.4-py2.py3-none-any.whl
>>> Collecting beautifulsoup4==4.4.1 (from -r requirements.txt (line 5))
>>>   Using cached beautifulsoup4-4.4.1-py2-none-any.whl
>>> Collecting blinker==1.3 (from -r requirements.txt (line 6))
>>> Collecting click==6.6 (from -r requirements.txt (line 7))
>>>   Using cached click-6.6-py2.py3-none-any.whl
>>> Collecting extras==0.0.3 (from -r requirements.txt (line 8))
>>> Collecting fixtures==2.0.0 (from -r requirements.txt (line 9))
>>>   Using cached fixtures-2.0.0-py2.py3-none-any.whl
>>> Collecting Flask==0.11.1 (from -r requirements.txt (line 10))
>>>   Using cached Flask-0.11.1-py2.py3-none-any.whl
>>> Collecting Flask-Babel==0.11.1 (from -r requirements.txt (line 11))
>>> Collecting Flask-Gravatar==0.4.2 (from -r requirements.txt (line 12))
>>>   Using cached Flask_Gravatar-0.4.2-py2.py3-none-any.whl
>>> Collecting Flask-HTMLmin==1.2 (from -r requirements.txt (line 13))
>>> Collecting Flask-Login==0.3.2 (from -r requirements.txt (line 14))
>>> Collecting Flask-Mail==0.9.1 (from -r requirements.txt (line 15))
>>> Collecting Flask-Migrate==2.0.3 (from -r requirements.txt (line 16))
>>> Collecting Flask-Principal==0.4.0 (from -r requirements.txt (line 17))
>>> Collecting Flask-Security==1.7.5 (from -r requirements.txt (line 18))
>>> Collecting Flask-SQLAlchemy==2.1 (from -r requirements.txt (line 19))
>>> Collecting Flask-WTF==0.12 (from -r requirements.txt (line 20))
>>>   Using cached Flask_WTF-0.12-py2-none-any.whl
>>> Collecting html5lib==1.0b3 (from -r requirements.txt (line 21))
>>> Collecting importlib==1.0.3 (from -r requirements.txt (line 22))
>>> Collecting itsdangerous==0.24 (from -r requirements.txt (line 23))
>>> Collecting Jinja2==2.7.3 (from -r

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Murtuza Zabuawala 
I'm able to run tests & pgAdmin4 on my machine using Python2.6.

--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

[image: https://community.postgresrocks.net/]


On Mon, Sep 11, 2017 at 2:08 PM, Dave Page  wrote:

> Murtuza, please look into this ASAP. I need the builds to go green so I
> can cut the release!
>
> On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins 
> wrote:
>
>> See > 6/display/redirect?page=changes>
>>
>> Changes:
>>
>> [Dave Page] Stick with the older Flask-Script module for Python 2.6
>>
>> --
>> Started by an SCM change
>> Started by an SCM change
>> Started by an SCM change
>> Started by an SCM change
>> Started by an SCM change
>> [EnvInject] - Loading node environment variables.
>> Building in workspace > ob/pgadmin4-master-python26/ws/>
>>  > git rev-parse --is-inside-work-tree # timeout=10
>> Fetching changes from the remote Git repository
>>  > git config remote.origin.url git://git.postgresql.org/git/pgadmin4.git
>> # timeout=10
>> Cleaning workspace
>>  > git rev-parse --verify HEAD # timeout=10
>> Resetting working tree
>>  > git reset --hard # timeout=10
>>  > git clean -fdx # timeout=10
>> Fetching upstream changes from git://git.postgresql.org/git/pgadmin4.git
>>  > git --version # timeout=10
>>  > git fetch --tags --progress git://git.postgresql.org/git/pgadmin4.git
>> +refs/heads/*:refs/remotes/origin/*
>>  > git rev-parse origin/master^{commit} # timeout=10
>> Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>> (origin/master)
>> Commit message: "Stick with the older Flask-Script module for Python 2.6"
>>  > git config core.sparsecheckout # timeout=10
>>  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>>  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 # timeout=10
>> [EnvInject] - Executing scripts and injecting environment variables after
>> the SCM step.
>> [EnvInject] - Injecting as environment variables the properties content
>> PYTHON_VERSION=2.6
>>
>> [EnvInject] - Variables injected successfully.
>> [pgadmin4-master-python26] $ /bin/sh -xe /tmp/jenkins154147539017300857
>> 7.sh
>> + > /ci/ci_runner.sh>
>> EXECUTING: Create pgAdmin config
>>
>> EXECUTING: Python tests
>>
>> Creating Python 2.6 virtual environment...
>>
>> New python executable in > ob/pgadmin4-master-python26/ws/pgadmin-venv/bin/python>
>> Installing setuptools, pip, wheel...done.
>> Running virtualenv with interpreter /usr/local/python-2.6/bin/python
>> DEPRECATION: Python 2.6 is no longer supported by the Python core team,
>> please upgrade your Python. A future version of pip will drop support for
>> Python 2.6
>> Collecting Babel==2.3.4 (from -r requirements.txt (line 4))
>>   Using cached Babel-2.3.4-py2.py3-none-any.whl
>> Collecting beautifulsoup4==4.4.1 (from -r requirements.txt (line 5))
>>   Using cached beautifulsoup4-4.4.1-py2-none-any.whl
>> Collecting blinker==1.3 (from -r requirements.txt (line 6))
>> Collecting click==6.6 (from -r requirements.txt (line 7))
>>   Using cached click-6.6-py2.py3-none-any.whl
>> Collecting extras==0.0.3 (from -r requirements.txt (line 8))
>> Collecting fixtures==2.0.0 (from -r requirements.txt (line 9))
>>   Using cached fixtures-2.0.0-py2.py3-none-any.whl
>> Collecting Flask==0.11.1 (from -r requirements.txt (line 10))
>>   Using cached Flask-0.11.1-py2.py3-none-any.whl
>> Collecting Flask-Babel==0.11.1 (from -r requirements.txt (line 11))
>> Collecting Flask-Gravatar==0.4.2 (from -r requirements.txt (line 12))
>>   Using cached Flask_Gravatar-0.4.2-py2.py3-none-any.whl
>> Collecting Flask-HTMLmin==1.2 (from -r requirements.txt (line 13))
>> Collecting Flask-Login==0.3.2 (from -r requirements.txt (line 14))
>> Collecting Flask-Mail==0.9.1 (from -r requirements.txt (line 15))
>> Collecting Flask-Migrate==2.0.3 (from -r requirements.txt (line 16))
>> Collecting Flask-Principal==0.4.0 (from -r requirements.txt (line 17))
>> Collecting Flask-Security==1.7.5 (from -r requirements.txt (line 18))
>> Collecting Flask-SQLAlchemy==2.1 (from -r requirements.txt (line 19))
>> Collecting Flask-WTF==0.12 (from -r requirements.txt (line 20))
>>   Using cached Flask_WTF-0.12-py2-none-any.whl
>> Collecting html5lib==1.0b3 (from -r requirements.txt (line 21))
>> Collecting importlib==1.0.3 (from -r requirements.txt (line 22))
>> Collecting itsdangerous==0.24 (from -r requirements.txt (line 23))
>> Collecting Jinja2==2.7.3 (from -r requirements.txt (line 24))
>> Collecting linecache2==1.0.0 (from -r requirements.txt (line 25))
>>   Using cached linecache2-1.0.0-py2.py3-none-any.whl
>> Collecting MarkupSafe==0.23 (from -r requirements.txt (line 26))
>> Collecting ordereddict (from

Re: Build failed in Jenkins: pgadmin4-master-python26 #436

2017-09-11 Thread Dave Page 
Murtuza, please look into this ASAP. I need the builds to go green so I can
cut the release!

On Mon, Sep 11, 2017 at 9:32 AM, pgAdmin 4 Jenkins 
wrote:

> See  436/display/redirect?page=changes>
>
> Changes:
>
> [Dave Page] Stick with the older Flask-Script module for Python 2.6
>
> --
> Started by an SCM change
> Started by an SCM change
> Started by an SCM change
> Started by an SCM change
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building in workspace  job/pgadmin4-master-python26/ws/>
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url git://git.postgresql.org/git/pgadmin4.git
> # timeout=10
> Cleaning workspace
>  > git rev-parse --verify HEAD # timeout=10
> Resetting working tree
>  > git reset --hard # timeout=10
>  > git clean -fdx # timeout=10
> Fetching upstream changes from git://git.postgresql.org/git/pgadmin4.git
>  > git --version # timeout=10
>  > git fetch --tags --progress git://git.postgresql.org/git/pgadmin4.git
> +refs/heads/*:refs/remotes/origin/*
>  > git rev-parse origin/master^{commit} # timeout=10
> Checking out Revision 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
> (origin/master)
> Commit message: "Stick with the older Flask-Script module for Python 2.6"
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 8b1aeadaf0347fb27bc7756cdf03aad32d03f3da
>  > git rev-list ac2512799e75eebc7612ee9ebe0ffd0841f25912 # timeout=10
> [EnvInject] - Executing scripts and injecting environment variables after
> the SCM step.
> [EnvInject] - Injecting as environment variables the properties content
> PYTHON_VERSION=2.6
>
> [EnvInject] - Variables injected successfully.
> [pgadmin4-master-python26] $ /bin/sh -xe /tmp/
> jenkins1541475390173008577.sh
> +  ws/ci/ci_runner.sh>
> EXECUTING: Create pgAdmin config
>
> EXECUTING: Python tests
>
> Creating Python 2.6 virtual environment...
>
> New python executable in  job/pgadmin4-master-python26/ws/pgadmin-venv/bin/python>
> Installing setuptools, pip, wheel...done.
> Running virtualenv with interpreter /usr/local/python-2.6/bin/python
> DEPRECATION: Python 2.6 is no longer supported by the Python core team,
> please upgrade your Python. A future version of pip will drop support for
> Python 2.6
> Collecting Babel==2.3.4 (from -r requirements.txt (line 4))
>   Using cached Babel-2.3.4-py2.py3-none-any.whl
> Collecting beautifulsoup4==4.4.1 (from -r requirements.txt (line 5))
>   Using cached beautifulsoup4-4.4.1-py2-none-any.whl
> Collecting blinker==1.3 (from -r requirements.txt (line 6))
> Collecting click==6.6 (from -r requirements.txt (line 7))
>   Using cached click-6.6-py2.py3-none-any.whl
> Collecting extras==0.0.3 (from -r requirements.txt (line 8))
> Collecting fixtures==2.0.0 (from -r requirements.txt (line 9))
>   Using cached fixtures-2.0.0-py2.py3-none-any.whl
> Collecting Flask==0.11.1 (from -r requirements.txt (line 10))
>   Using cached Flask-0.11.1-py2.py3-none-any.whl
> Collecting Flask-Babel==0.11.1 (from -r requirements.txt (line 11))
> Collecting Flask-Gravatar==0.4.2 (from -r requirements.txt (line 12))
>   Using cached Flask_Gravatar-0.4.2-py2.py3-none-any.whl
> Collecting Flask-HTMLmin==1.2 (from -r requirements.txt (line 13))
> Collecting Flask-Login==0.3.2 (from -r requirements.txt (line 14))
> Collecting Flask-Mail==0.9.1 (from -r requirements.txt (line 15))
> Collecting Flask-Migrate==2.0.3 (from -r requirements.txt (line 16))
> Collecting Flask-Principal==0.4.0 (from -r requirements.txt (line 17))
> Collecting Flask-Security==1.7.5 (from -r requirements.txt (line 18))
> Collecting Flask-SQLAlchemy==2.1 (from -r requirements.txt (line 19))
> Collecting Flask-WTF==0.12 (from -r requirements.txt (line 20))
>   Using cached Flask_WTF-0.12-py2-none-any.whl
> Collecting html5lib==1.0b3 (from -r requirements.txt (line 21))
> Collecting importlib==1.0.3 (from -r requirements.txt (line 22))
> Collecting itsdangerous==0.24 (from -r requirements.txt (line 23))
> Collecting Jinja2==2.7.3 (from -r requirements.txt (line 24))
> Collecting linecache2==1.0.0 (from -r requirements.txt (line 25))
>   Using cached linecache2-1.0.0-py2.py3-none-any.whl
> Collecting MarkupSafe==0.23 (from -r requirements.txt (line 26))
> Collecting ordereddict (from -r requirements.txt (line 27))
>  ws/pgadmin-venv/lib/python2.6/site-packages/pip/_vendor/
> requests/packages/urllib3/util/ssl_.py>:318: SNIMissingWarning: An HTTPS
> request has been made, but the SNI (Subject Name Indication) extension to
> TLS is not available on this platform. This may cause the server to present
> an incorrect TLS certificate, which can cause