See <https://ci-builds.apache.org/job/Allura/job/Allura-py3.11/46/display/redirect?page=changes>
Changes: [dbrondsema] avoid unhandled error on bad input to /nf/markdown_to_html ------------------------------------------ [...truncated 123.01 KB...] Node.js 10.x is no longer actively supported! You will not receive security or critical stability updates for this version. You should migrate to a supported version of Node.js as soon as possible. Use the installation script that corresponds to the version of Node.js you wish to install. e.g. * https://deb.nodesource.com/setup_12.x ? Node.js 12 LTS "Erbium" * https://deb.nodesource.com/setup_14.x ? Node.js 14 LTS "Fermium" (recommended) * https://deb.nodesource.com/setup_16.x ? Node.js 16 "Gallium" Please see https://github.com/nodejs/Release for details about which version may be appropriate for you. The NodeSource Node.js distributions repository contains information both about supported versions of Node.js and supported Linux distributions. To learn more about usage, see the repository: https://github.com/nodesource/distributions ================================================================================ ================================================================================ Continuing in 20 seconds ... ## Installing the NodeSource Node.js 10.x repo... ## Populating apt-get cache... + apt-get update Get:1 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic InRelease [15.9 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:4 http://ppa.launchpad.net/git-core/ppa/ubuntu bionic InRelease [20.8 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [3358 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:7 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic/main amd64 Packages [447 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [83.3 kB] Get:9 http://ppa.launchpad.net/git-core/ppa/ubuntu bionic/main amd64 Packages [3162 B] Get:10 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB] Get:11 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1631 kB] Get:12 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [23.8 kB] Get:13 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [1668 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [3771 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [1709 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2403 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [30.8 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [64.0 kB] Get:22 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [20.6 kB] Fetched 28.1 MB in 5s (5699 kB/s) Reading package lists... ## Confirming "bionic" is supported... + curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/bionic/Release' ## Adding the NodeSource signing key to your keyring... + curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null ## Creating apt sources list file for the NodeSource Node.js 10.x repo... + echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_10.x bionic main' > /etc/apt/sources.list.d/nodesource.list + echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_10.x bionic main' >> /etc/apt/sources.list.d/nodesource.list ## Running `apt-get update` for you... + apt-get update Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu bionic InRelease Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:6 https://deb.nodesource.com/node_10.x bionic InRelease [4584 B] Hit:7 http://ppa.launchpad.net/git-core/ppa/ubuntu bionic InRelease Get:8 https://deb.nodesource.com/node_10.x bionic/main amd64 Packages [767 B] Fetched 5351 B in 2s (3547 B/s) Reading package lists... ## Run `sudo apt-get install -y nodejs` to install Node.js 10.x and npm ## You may also need development tools to build native addons: sudo apt-get install gcc g++ make ## To install the Yarn package manager, run: curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt-get update && sudo apt-get install yarn Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libpython2.7-minimal python-minimal python2.7-minimal Suggested packages: binfmt-support Recommended packages: libpython2.7-stdlib python python2.7 The following NEW packages will be installed: libpython2.7-minimal nodejs python-minimal python2.7-minimal 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 17.6 MB of archives. After this operation, 87.3 MB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-minimal amd64 2.7.17-1~18.04ubuntu1.11 [335 kB] Get:2 https://deb.nodesource.com/node_10.x bionic/main amd64 nodejs amd64 10.24.1-1nodesource1 [15.9 MB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7-minimal amd64 2.7.17-1~18.04ubuntu1.11 [1294 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-minimal amd64 2.7.15~rc1-1 [28.1 kB] [91mdebconf: delaying package configuration, since apt-utils is not installed [0mFetched 17.6 MB in 1s (13.7 MB/s) Selecting previously unselected package libpython2.7-minimal:amd64. (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 16599 files and directories currently installed.) Preparing to unpack .../libpython2.7-minimal_2.7.17-1~18.04ubuntu1.11_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.17-1~18.04ubuntu1.11) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.17-1~18.04ubuntu1.11_amd64.deb ... Unpacking python2.7-minimal (2.7.17-1~18.04ubuntu1.11) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.15~rc1-1_amd64.deb ... Unpacking python-minimal (2.7.15~rc1-1) ... Selecting previously unselected package nodejs. Preparing to unpack .../nodejs_10.24.1-1nodesource1_amd64.deb ... Unpacking nodejs (10.24.1-1nodesource1) ... Setting up libpython2.7-minimal:amd64 (2.7.17-1~18.04ubuntu1.11) ... Setting up python2.7-minimal (2.7.17-1~18.04ubuntu1.11) ... Setting up python-minimal (2.7.15~rc1-1) ... Setting up nodejs (10.24.1-1nodesource1) ... Removing intermediate container bf4bfbd1501a ---> a4613312d255 Step 8/13 : RUN locale-gen en_US.UTF-8 ---> Running in 0b028d425fd2 Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. Removing intermediate container 0b028d425fd2 ---> 0a1c79c13e7f Step 9/13 : ENV LANG en_US.UTF-8 ---> Running in b26a9347fd6d Removing intermediate container b26a9347fd6d ---> 9ac51fe89140 Step 10/13 : ENV USER root ---> Running in d6dbc628289c Removing intermediate container d6dbc628289c ---> 0a594c728b3d Step 11/13 : WORKDIR /allura ---> Running in 14c7a032122d Removing intermediate container 14c7a032122d ---> 444d7830d591 Step 12/13 : ENV PYTHONUNBUFFERED 1 ---> Running in 22c2849a1799 Removing intermediate container 22c2849a1799 ---> 779e5d8e7320 Step 13/13 : CMD gunicorn --paste Allura/docker-dev.ini -b :8088 --reload ---> Running in 16b58dabdefa Removing intermediate container 16b58dabdefa ---> 1b334e1aa91d Successfully built 1b334e1aa91d Successfully tagged allura-web:latest Image for service web was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`. Creating allura_mongo_1 ... Creating allura_solr_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_solr_1 is up-to-date allura_mongo_1 is up-to-date Creating allura_web_1 ... Creating allura_web_1 ... done ============================================================================= Docker Container Info: ============================================================================= Error response from daemon: Container 9dfdd6157e73c3060fea40f48f0c2dec8693368119d865806d91c896c5ce3dba is not running ============================================================================= Setup: tests ============================================================================= ============================================================================= Run: tests ============================================================================= ============================================================================= Shutdown ============================================================================= Stopping allura_solr_1 ... Stopping allura_mongo_1 ... Stopping allura_solr_1 ... done Stopping allura_mongo_1 ... done Removing allura_web_1 ... Removing allura_solr_1 ... Removing allura_mongo_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: 892bbead7d93c52690b10d8f3c2c846a4dfd04c9b91b7997d543810604918263 068abb8d11d68d2215b69a2f00097b9fd02c5c33114585048a249fa01581d1ab b8af3c698538ff60473c8bfe9190b17ae5242aa6b63eef759d52d7e0a1dac14a c599920ea47e51e9ec7274730971c92655559921ddf386730f2cf38431113c48 9b746c5cb564e484e725b0d7d85b5fbae845736a55d125c9379bcd5edee76caa 33d70ddbb91ef1f5f2b20e3e0c197067d73425b1bd5a21d7b95282f27bcd8caa 0b089212b1ceea4413418cdd5cc287f975153551795967929c210bf9059437fa 0de3b298141b85ab72548eff2b189ea7dbc1d31669d3f389ce00a12a5e372a1b 50cde2e4719180117fd80db3de2370045e7abb605bcb1209d33517d036428d83 0a35fefba33cf7eaf7b5a8841f2115cf65da993ba0b5432fa939b1d27a86c198 d433fb3c23679f2f06effa111adec7600b076fd360f9ab93e4023a9de88e550a a81990937fd9eab1a4217de1343c5948f2319c7af36bb8fc3cb58041e95be960 e722814711f213e46a7dac988a63da02c126c33ecf13cd87dbee2ca3bed9e5b0 892b413b9312143e8c34041e2fbd78ed5358dbedd3a577cf0a13ec4db7afd495 Total reclaimed space: 2.61GB 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?
