Build failed in Jenkins: pgadmin4-master-python35 #556

Поиск
Список
Период
Сортировка
От pgAdmin 4 Jenkins
Тема Build failed in Jenkins: pgadmin4-master-python35 #556
Дата
Msg-id 1766576552.228.1522846267119.JavaMail.jenkins@jenkins.pgadmin.org
обсуждение исходный текст
Ответ на Build failed in Jenkins: pgadmin4-master-python35 #555  (pgAdmin 4 Jenkins <jenkins@pgadmin.org>)
Ответы Jenkins build is back to normal : pgadmin4-master-python35 #557  (pgAdmin 4 Jenkins <jenkins@pgadmin.org>)
Список pgadmin-hackers
See <https://jenkins.pgadmin.org/job/pgadmin4-master-python35/556/display/redirect?page=changes>

Changes:

[Dave Page] Typo fix.

[Dave Page] Another attempt to fix the Python 2.6 deps.

------------------------------------------
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
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building in workspace <https://jenkins.pgadmin.org/job/pgadmin4-master-python35/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 a95775ae49e47fe1f289c514bb936a726010033c (origin/master)
Commit message: "Another attempt to fix the Python 2.6 deps."
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a95775ae49e47fe1f289c514bb936a726010033c
 > git rev-list c0cfc9f29b1e8ac1099a135ff7acf327576691fd # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - Injecting as environment variables the properties content 
PYTHON_VERSION=3.5

[EnvInject] - Variables injected successfully.
[pgadmin4-master-python35] $ /bin/sh -xe /tmp/jenkins3013319889388325584.sh
+ <https://jenkins.pgadmin.org/job/pgadmin4-master-python35/ws/ci/ci_runner.sh>
EXECUTING: Create pgAdmin config

EXECUTING: Python tests

Creating Python 3.5 virtual environment...

Using base prefix '/usr/local/python-3.5'
New python executable in <https://jenkins.pgadmin.org/job/pgadmin4-master-python35/ws/pgadmin-venv/bin/python3>
Also creating executable in <https://jenkins.pgadmin.org/job/pgadmin4-master-python35/ws/pgadmin-venv/bin/python>
Installing setuptools, pip, wheel...done.
Running virtualenv with interpreter /usr/local/python-3.5/bin/python3
Double requirement given: Flask-Security>=3.0.0 (from -r requirements.txt (line 40)) (already in Flask-Security==3.0.0
(from-r requirements.txt (line 15)), name='Flask-Security')
 
ERROR: Failed to install the application requirements.
ERROR: Error detected when running the Python tests.
Build step 'Execute shell' marked build as failure


В списке pgadmin-hackers по дате отправления:

Предыдущее
От: pgAdmin 4 Jenkins
Дата:
Сообщение: Jenkins build is back to normal : pgadmin4-master-python34 #546
Следующее
От: pgAdmin 4 Jenkins
Дата:
Сообщение: Build failed in Jenkins: pgadmin4-master-python27 #557