See <https://ci-builds.apache.org/job/Allura/job/Allura-py3.8/319/display/redirect>
Changes: ------------------------------------------ [...truncated 13.69 KB...] Preparing metadata (setup.py): finished with status 'done' Installing collected packages: AlluraTest Running setup.py develop for AlluraTest Successfully installed AlluraTest-0.1 # setting up ForgeActivity Obtaining file:///allura/ForgeActivity Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: allura in /allura/Allura (from ForgeActivity==0.1.dev0) (0.1.dev0) Installing collected packages: ForgeActivity Running setup.py develop for ForgeActivity Successfully installed ForgeActivity-0.1.dev0 # setting up ForgeBlog Obtaining file:///allura/ForgeBlog Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: allura in /allura/Allura (from ForgeBlog==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeBlog Running setup.py develop for ForgeBlog Successfully installed ForgeBlog-0.0.dev0 # setting up ForgeChat Obtaining file:///allura/ForgeChat Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: allura in /allura/Allura (from ForgeChat==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeChat Running setup.py develop for ForgeChat Successfully installed ForgeChat-0.0.dev0 # setting up ForgeDiscussion Obtaining file:///allura/ForgeDiscussion Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeDiscussion==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeDiscussion Running setup.py develop for ForgeDiscussion Successfully installed ForgeDiscussion-0.0.dev0 # setting up ForgeFeedback Obtaining file:///allura/ForgeFeedback Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeFeedback==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeFeedback Running setup.py develop for ForgeFeedback Successfully installed ForgeFeedback-0.0.dev0 # setting up ForgeFiles Obtaining file:///allura/ForgeFiles Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Installing collected packages: ForgeFiles Running setup.py develop for ForgeFiles Successfully installed ForgeFiles-0.1.0.dev0 # setting up ForgeGit Obtaining file:///allura/ForgeGit Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeGit==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeGit Running setup.py develop for ForgeGit Successfully installed ForgeGit-0.0.dev0 # setting up ForgeImporters Obtaining file:///allura/ForgeImporters Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeImporters==0.0.0.dev0) (0.1.dev0) Installing collected packages: ForgeImporters Running setup.py develop for ForgeImporters Successfully installed ForgeImporters-0.0.0.dev0 # setting up ForgeLink Obtaining file:///allura/ForgeLink Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeLink==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeLink Running setup.py develop for ForgeLink Successfully installed ForgeLink-0.0.dev0 # setting up ForgeShortUrl Obtaining file:///allura/ForgeShortUrl Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeShortUrl==0.0.0.dev0) (0.1.dev0) Installing collected packages: ForgeShortUrl Running setup.py develop for ForgeShortUrl Successfully installed ForgeShortUrl-0.0.0.dev0 # setting up ForgeSVN Obtaining file:///allura/ForgeSVN Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeSVN==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeSVN Running setup.py develop for ForgeSVN Successfully installed ForgeSVN-0.0.dev0 # setting up ForgeTracker Obtaining file:///allura/ForgeTracker Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeTracker==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeTracker Running setup.py develop for ForgeTracker Successfully installed ForgeTracker-0.0.dev0 # setting up ForgeUserStats Obtaining file:///allura/ForgeUserStats Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: allura in /allura/Allura (from ForgeUserStats==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeUserStats Running setup.py develop for ForgeUserStats Successfully installed ForgeUserStats-0.0.dev0 # setting up ForgeWiki Obtaining file:///allura/ForgeWiki Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'done' Requirement already satisfied: Allura in /allura/Allura (from ForgeWiki==0.0.dev0) (0.1.dev0) Installing collected packages: ForgeWiki Running setup.py develop for ForgeWiki Successfully installed ForgeWiki-0.0.dev0 Installing npm packages npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm WARN deprecated source-map-url@0.3.0: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated exists-sync@0.0.4: Please replace with usage of fs.existsSync npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated lodash-node@2.4.1: This package is discontinued. Use lodash@^4.0.0. npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. added 426 packages, and audited 427 packages in 24s 8 packages are looking for funding run `npm fund` for details 27 vulnerabilities (2 moderate, 19 high, 6 critical) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. npm notice npm notice New major version of npm available! 8.19.4 -> 10.3.0 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.3.0> npm notice Run `npm install -g npm@10.3.0` to update! npm notice Compiling JS > allura@0.0.0 build > rm -rf Allura/allura/public/nf/js/build/; broccoli build > Allura/allura/public/nf/js/build/ Done ============================================================================= Starting up docker containers ============================================================================= Container allura-mongo-1 Running Container allura-solr-1 Running Container allura-web-1 Creating Container allura-web-1 Created Container allura-web-1 Starting Container allura-web-1 Started ============================================================================= Docker Container Info: ============================================================================= python path: /allura-data/virtualenv/bin/python Python 3.8.18 git version 2.34.1 svn, version 1.14.1 (r1886195) compiled May 21 2022, 10:52:35 on x86_64-pc-linux-gnu Copyright (C) 2021 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - using serf 1.3.9 (compiled with 1.3.9) - handles 'http' scheme - handles 'https' scheme The following authentication credential caches are available: * Gnome Keyring * GPG-Agent * KWallet (KDE) pip: pip 23.3.2 from /allura-data/virtualenv/lib/python3.8/site-packages/pip (python 3.8) npm: 8.19.4 whoami: root ============================================================================= Setup: tests ============================================================================= Error response from daemon: Container c18dacb159ee73f3a58d5a84d90be59aba2bef0e2d075847e22c2d287d10ce62 is not running ============================================================================= Run: tests ============================================================================= service "web" is not running service "web" is not running service "web" is not running ============================================================================= Shutdown ============================================================================= Container allura-web-1 Stopping Container allura-web-1 Stopped Container allura-web-1 Removing Container allura-web-1 Removed Container allura-solr-1 Stopping Container allura-mongo-1 Stopping Container allura-solr-1 Stopped Container allura-solr-1 Removing Container allura-mongo-1 Stopped Container allura-mongo-1 Removing Container allura-mongo-1 Removed Container allura-solr-1 Removed Network allura_default Removing Network allura_default Removed Total reclaimed space: 0B Deleted Volumes: 8f7e41ea7f2d5c9c2f06444e31af2637764b77b08290bcd19b839ac3ca410798 Total reclaimed space: 0B 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?
