See 
<https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/240/display/redirect?page=changes>

Changes:

[Dillon Walls] fix dependency-check warning for cryptography<41.0.0


------------------------------------------
[...truncated 121.36 KB...]
#6 58.14 Setting up perl-modules-5.26 (5.26.1-6ubuntu0.7) ...
#6 58.29 Setting up libgdbm5:amd64 (1.14.1-6) ...
#6 58.45 Setting up libkrb5support0:amd64 (1.16-2ubuntu0.4) ...
#6 58.60 Setting up libxml2:amd64 (2.9.4+dfsg1-6.1ubuntu1.9) ...
#6 58.75 Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.23) ...
#6 59.11 Setting up libaprutil1:amd64 (1.6.1-2ubuntu0.1) ...
#6 59.26 Setting up libheimbase1-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 59.41 Setting up openssl (1.1.1-1ubuntu2.1~18.04.23) ...
#6 59.62 Setting up libsqlite3-0:amd64 (3.22.0-1ubuntu0.7) ...
#6 59.78 Setting up liblua5.2-0:amd64 (5.2.4-1.1build1) ...
#6 59.94 Setting up libgdbm-compat4:amd64 (1.14.1-6) ...
#6 60.09 Setting up libkeyutils1:amd64 (1.5.9-9.2ubuntu2.1) ...
#6 60.24 Setting up ca-certificates (20230311ubuntu0.18.04.1) ...
#6 61.33 Updating certificates in /etc/ssl/certs...
#6 62.59 137 added, 0 removed; done.
#6 62.81 Setting up libpython2.7-stdlib:amd64 (2.7.17-1~18.04ubuntu1.11) ...
#6 62.96 Setting up libk5crypto3:amd64 (1.16-2ubuntu0.4) ...
#6 63.11 Setting up libwind0-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 63.26 Setting up libaprutil1-dbd-sqlite3:amd64 (1.6.1-2ubuntu0.1) ...
#6 63.70 Setting up apache2-utils (2.4.29-1ubuntu4.27) ...
#6 63.86 Setting up libasn1-8-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 64.01 Setting up libhcrypto4-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 64.16 Setting up python2.7 (2.7.17-1~18.04ubuntu1.11) ...
#6 65.52 Setting up libhx509-5-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 65.67 Setting up libpython-stdlib:amd64 (2.7.15~rc1-1) ...
#6 65.82 Setting up libperl5.26:amd64 (5.26.1-6ubuntu0.7) ...
#6 65.97 Setting up libpython2.7:amd64 (2.7.17-1~18.04ubuntu1.11) ...
#6 66.12 Setting up libkrb5-3:amd64 (1.16-2ubuntu0.4) ...
#6 66.27 Setting up libkrb5-26-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 66.42 Setting up libheimntlm0-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 66.57 Setting up python (2.7.15~rc1-1) ...
#6 66.80 Setting up python-idna (2.6-1) ...
#6 67.92 Setting up python-certifi (2018.1.18-2) ...
#6 68.89 Setting up python-pkg-resources (39.0.1-2ubuntu0.1) ...
#6 69.96 Setting up libgssapi-krb5-2:amd64 (1.16-2ubuntu0.4) ...
#6 70.11 Setting up perl (5.26.1-6ubuntu0.7) ...
#6 70.33 Setting up python-six (1.11.0-2) ...
#6 71.35 Setting up libgssapi3-heimdal:amd64 (7.5.0+dfsg-1ubuntu0.4) ...
#6 71.50 Setting up python-urllib3 (1.22-1ubuntu0.18.04.2) ...
#6 72.54 Setting up python-chardet (3.0.4-1) ...
#6 73.81 Setting up liberror-perl (0.17025-1) ...
#6 73.96 Setting up libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.11) ...
#6 74.11 Setting up python-requests (2.18.4-2ubuntu0.1) ...
#6 75.02 Setting up libaprutil1-ldap:amd64 (1.6.1-2ubuntu0.1) ...
#6 75.17 Setting up libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.24) ...
#6 75.32 Setting up libcurl4:amd64 (7.58.0-2ubuntu3.24) ...
#6 75.47 Setting up apache2-bin (2.4.29-1ubuntu4.27) ...
#6 75.62 Setting up git (1:2.17.1-1ubuntu0.18) ...
#6 75.84 Setting up apache2 (2.4.29-1ubuntu4.27) ...
#6 83.85 Enabling module mpm_event.
#6 83.90 Enabling module authz_core.
#6 83.91 Enabling module authz_host.
#6 83.96 Enabling module authn_core.
#6 83.96 Enabling module auth_basic.
#6 84.01 Enabling module access_compat.
#6 84.06 Enabling module authn_file.
#6 84.11 Enabling module authz_user.
#6 84.16 Enabling module alias.
#6 84.21 Enabling module dir.
#6 84.26 Enabling module autoindex.
#6 84.31 Enabling module env.
#6 84.36 Enabling module mime.
#6 84.41 Enabling module negotiation.
#6 84.46 Enabling module setenvif.
#6 84.52 Enabling module filter.
#6 84.58 Enabling module deflate.
#6 84.63 Enabling module status.
#6 84.68 Enabling module reqtimeout.
#6 84.75 Enabling conf charset.
#6 84.81 Enabling conf localized-error-pages.
#6 84.87 Enabling conf other-vhosts-access-log.
#6 84.93 Enabling conf security.
#6 84.99 Enabling conf serve-cgi-bin.
#6 85.05 Enabling site 000-default.
#6 85.57 invoke-rc.d: could not determine current runlevel
#6 85.57 invoke-rc.d: policy-rc.d denied execution of start.
#6 85.82 Setting up curl (7.58.0-2ubuntu3.24) ...
#6 85.98 Setting up libapache2-mod-python (3.3.1-11ubuntu2) ...
#6 86.27 apache2_invoke: Enable module python
#6 86.32 invoke-rc.d: could not determine current runlevel
#6 86.32 invoke-rc.d: policy-rc.d denied execution of restart.
#6 87.22 Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
#6 87.37 Processing triggers for ca-certificates (20230311ubuntu0.18.04.1) ...
#6 87.43 Updating certificates in /etc/ssl/certs...
#6 88.28 0 added, 0 removed; done.
#6 88.28 Running hooks in /etc/ca-certificates/update.d...
#6 88.28 done.
#6 DONE 89.3s

#7 [ 3/10] RUN a2enmod cgi proxy proxy_http
#7 1.557 Your MPM seems to be threaded. Selecting cgid instead of cgi.
#7 1.557 Enabling module cgid.
#7 1.563 Enabling module proxy.
#7 1.569 Considering dependency proxy for proxy_http:
#7 1.569 Module proxy already enabled
#7 1.569 Enabling module proxy_http.
#7 1.574 To activate the new configuration, you need to run:
#7 1.574   service apache2 restart
#7 DONE 2.3s

#8 [ 4/10] ADD ./git-http.conf /etc/apache2/sites-available/
#8 DONE 1.1s

#9 [ 5/10] RUN a2dissite 000-default.conf
#9 1.146 Site 000-default disabled.
#9 1.146 To activate the new configuration, you need to run:
#9 1.146   service apache2 reload
#9 DONE 1.8s

#10 [ 6/10] RUN a2ensite git-http.conf
#10 1.429 Enabling site git-http.
#10 1.434 To activate the new configuration, you need to run:
#10 1.434   service apache2 reload
#10 DONE 2.2s

#11 [ 7/10] RUN apachectl configtest
#11 1.421 AH00558: apache2: Could not reliably determine the server's fully 
qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally 
to suppress this message
#11 1.421 Syntax OK
#11 DONE 2.1s

#12 [ 8/10] ADD git-http-backend-wrapper.sh /usr/lib/git-core
#12 DONE 1.1s

#13 [ 9/10] RUN adduser www-data sudo
#13 1.238 Adding user `www-data' to group `sudo' ...
#13 1.241 Adding user www-data to group sudo
#13 1.450 Done.
#13 DONE 2.0s

#14 [10/10] RUN echo '%sudo  ALL=(ALL) NOPASSWD:ALL' > 
/etc/sudoers.d/sudo_group_passwordless
#14 DONE 2.1s

#15 exporting to image
#15 exporting layers
#15 exporting layers 4.5s done
#15 writing image 
sha256:5fd65ffa62be126236c918807f97eb2d08f16f9d222383fcdd760500f49896aa 0.0s 
done
#15 naming to docker.io/library/allura_http
#15 naming to docker.io/library/allura_http 0.1s done
#15 DONE 4.6s

=============================================================================
Setup: venv, pip, pysvn, ./rebuild-all.sh, npm, etc.
=============================================================================
Creating network "allura_default" with the default driver
Pulling solr (solr:6-alpine)...
6-alpine: Pulling from library/solr
Digest: sha256:4f63093698313437a49b2f945c4b1545c9e3a655f52581bc6e01ea006fae132e
Status: Downloaded newer image for solr:6-alpine
Pulling mongo (mongo:4.2)...
4.2: Pulling from library/mongo
Digest: sha256:3938c93865f4a33a722209fe1af2f6f93b7053cab6240ba173140b867740c5ea
Status: Downloaded newer image for mongo:4.2
Creating allura_solr_1 ... 
Creating allura_mongo_1 ... 
Creating allura_solr_1  ... done
Creating allura_mongo_1 ... done
Creating allura_web_run ... 
Creating allura_web_run ... done

Running scripts/init-docker-dev.sh

Creating SCM directories

Creating directory for SOLR data

Changing it's permissions to 777 so that container will have access to it

Creating virtualenv

The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

    apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/allura-data/virtualenv/bin/python3.7', '-Im', 'ensurepip', 
'--upgrade', '--default-pip']

1

=============================================================================
Starting up docker containers
=============================================================================
allura_mongo_1 is up-to-date
allura_solr_1 is up-to-date
Creating allura_web_1 ... 
Creating allura_web_1 ... done

=============================================================================
Docker Container Info:
=============================================================================
Error response from daemon: Container 
01524ab6bbafd4cff17f895a0eb093c90c6446f896fbbdeef722140c8c45b16c is not running

=============================================================================
Setup: tests
=============================================================================

=============================================================================
Run: tests
=============================================================================

=============================================================================
Shutdown
=============================================================================
Stopping allura_mongo_1 ... 
Stopping allura_solr_1  ... 
Stopping allura_solr_1  ... done
Stopping allura_mongo_1 ... done
Removing allura_web_1   ... 
Removing allura_mongo_1 ... 
Removing allura_solr_1  ... 
Removing allura_web_1   ... done
Removing allura_mongo_1 ... done
Removing allura_solr_1  ... done
Removing network allura_default
Total reclaimed space: 0B
Deleted Volumes:
4439fecd8060dc362a8f55b3b36af44bc34356e5a6dc625bc371dc290cf41d8e
a6c20535fe995116a4b5b6f38e1a008a68d28e1dbcd48402a3d6d42a6138f0f3
dcb52d19b51d9b2a7798324e4bd0b88f2bcd27d673c940bd705ef6ff72091969
73f18a486db147322026627f441c9eb6a5fde0317a4a00c3de88ba93a5392bf1
7de1616067cf2c0ca858e0ae8d2de4da845caa5e8044cf8de52a47269abf124d
84d2bea6159faa927647db4d786b9a6b3b4dcb98ce243813bf75e8439fe49a0b
e84bc35a1ad414d7acac73f18fdcdbf3665b3018a73d8bca99302d5e3bd5f575
1f7084f2aa4882d02ee68a66859c6c5839b2ae80d49632f4b121fafa84c6fb88
53acfd5a2ed811c7a16256d2f2a94337b2e6856cefdbca2d959902e8b9755468
0195f2085ca7a6f188daa39ebee7a8377ac3babf50ec01349942d5656850dbe9
8b0c819f9a0412dfc00e0a011e98e6151a491bb0b37cd31d82cd39b403dbec05
969eee7a8f03b584c4eafd6e59f781a0c801f1906dd5d27e46c0d250765e91b2
7959c15d79210eb740f0452e0c523661ce9fcb435272587467beea4fe8947d1e
c14204bc91e9a1b95b67a7e5d3c2a85f67e89f58f57d933d585706ec5a3c52e3
f6d4d6a0b254ad2cf75ff3d5b60ac14f00bf3ca28854422185a70a2ce2fd28b4
4c322694ec06ab07a5df48d98715136e4c50176c2837d2493db06821b95bb4aa
3ec85c6fb36b31b75434b2d8b929e90ce1aa757cf4bc621298d129871dae0a33
a99572234a1f6e23924a6d5bcbfd3e974a21275b89c68725b2645e014204a468
88f842108c13cd1934e6aa38aca22b2c21fab5ab120addad0bc042bceae3f191
621eef3406b5561e176b5803898235d02835b6fe376a9eebb6c7eb8869da5ca9
21a5db3b858f8e7e787b11fca729bd67dca5148c59e2010e7bfcc5aaac2e5752
aaa9bd874e5ab76271109f672319bc87463bb79c1180c56690f6639b8db02fe6
ca5ab7c149d603c045ffac7e5c06e458678c9d115366f6d96afc4e0249aea1e3
513007cb6d632fdb9ae2189fae52c252cb708b1180f9ce75d12b524e6a2db259
01b2fd7cf51cc04e83942fbe75152d379d2241c7171cd8531433c2d507cd99d7

Total reclaimed space: 4.46GB
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?

Reply via email to