See <https://builds.apache.org/job/Allura/1015/changes>
Changes: [heiths] On moderation page, if artifact can't be loaded, don't error out but be ------------------------------------------ [...truncated 1722 lines...] npm http GET https://registry.npmjs.org/eslint npm http GET https://registry.npmjs.org/eslint-config-xo npm http GET https://registry.npmjs.org/eslint-config-xo-react npm http GET https://registry.npmjs.org/eslint-plugin-html npm http GET https://registry.npmjs.org/eslint-plugin-react npm http GET https://registry.npmjs.org/esprima-fb npm ERR! Error: failed to fetch from registry: broccoli-cli npm ERR! at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12 npm ERR! at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9) npm ERR! at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18) npm ERR! at Request.callback (/usr/lib/nodejs/request/main.js:119:22) npm ERR! at Request.<anonymous> (/usr/lib/nodejs/request/main.js:212:58) npm ERR! at Request.emit (events.js:88:20) npm ERR! at ClientRequest.<anonymous> (/usr/lib/nodejs/request/main.js:412:12) npm ERR! at ClientRequest.emit (events.js:67:17) npm ERR! at HTTPParser.onIncoming (http.js:1261:11) npm ERR! at HTTPParser.onHeadersComplete (http.js:102:31) npm ERR! You may report this log at: npm ERR! <http://bugs.debian.org/npm> npm ERR! or use npm ERR! reportbug --attach /x1/jenkins/jenkins-slave/workspace/Allura/npm-debug.log npm npm ERR! npm ERR! System Linux 3.2.0-101-generic npm ERR! command "node" "/usr/bin/npm" "install" npm ERR! cwd /x1/jenkins/jenkins-slave/workspace/Allura npm ERR! node -v v0.6.12 npm ERR! npm -v 1.1.4 npm ERR! message failed to fetch from registry: broccoli-cli npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /x1/jenkins/jenkins-slave/workspace/Allura/npm-debug.log npm not ok retrying npm install npm http GET https://registry.npmjs.org/babel-eslint npm http GET https://registry.npmjs.org/broccoli npm http GET https://registry.npmjs.org/broccoli-babel-transpiler npm http GET https://registry.npmjs.org/broccoli-cli npm http GET https://registry.npmjs.org/broccoli-funnel npm http GET https://registry.npmjs.org/broccoli-merge-trees npm http GET https://registry.npmjs.org/broccoli-sourcemap-concat npm http GET https://registry.npmjs.org/broccoli-timepiece npm http GET https://registry.npmjs.org/broccoli-uglify-js npm http GET https://registry.npmjs.org/eslint npm http GET https://registry.npmjs.org/eslint-config-xo npm http GET https://registry.npmjs.org/eslint-config-xo-react npm http GET https://registry.npmjs.org/eslint-plugin-html npm http GET https://registry.npmjs.org/eslint-plugin-react npm http GET https://registry.npmjs.org/esprima-fb npm ERR! Error: failed to fetch from registry: broccoli-cli npm ERR! at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12 npm ERR! at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9) npm ERR! at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18) npm ERR! at Request.callback (/usr/lib/nodejs/request/main.js:119:22) npm ERR! at Request.<anonymous> (/usr/lib/nodejs/request/main.js:212:58) npm ERR! at Request.emit (events.js:88:20) npm ERR! at ClientRequest.<anonymous> (/usr/lib/nodejs/request/main.js:412:12) npm ERR! at ClientRequest.emit (events.js:67:17) npm ERR! at HTTPParser.onIncoming (http.js:1261:11) npm ERR! at HTTPParser.onHeadersComplete (http.js:102:31) npm ERR! You may report this log at: npm ERR! <http://bugs.debian.org/npm> npm ERR! or use npm ERR! reportbug --attach /x1/jenkins/jenkins-slave/workspace/Allura/npm-debug.log npm npm ERR! npm ERR! System Linux 3.2.0-101-generic npm ERR! command "node" "/usr/bin/npm" "install" npm ERR! cwd /x1/jenkins/jenkins-slave/workspace/Allura npm ERR! node -v v0.6.12 npm ERR! npm -v 1.1.4 npm ERR! message failed to fetch from registry: broccoli-cli npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /x1/jenkins/jenkins-slave/workspace/Allura/npm-debug.log npm not ok Not running tests for virtualenv-1.9.1, since it isn't set up <DummyProcess(Thread-2, started daemon 140635855361792)> running `nosetests --with-xunitmp --cover-package=alluratest --processes=4 --process-timeout=360` in AlluraTest <DummyProcess(Thread-1, started daemon 140635863754496)> running `nosetests allura/tests/ --with-xunitmp --cover-package=allura --processes=4 --process-timeout=360` in Allura <DummyProcess(Thread-3, started daemon 140635846969088)> running `nosetests --with-xunitmp --cover-package=forgeactivity --processes=4 --process-timeout=360` in ForgeActivity <DummyProcess(Thread-4, started daemon 140635838576384)> running `nosetests --with-xunitmp --cover-package=forgeblog --processes=4 --process-timeout=360` in ForgeBlog <DummyProcess(Thread-5, started daemon 140635830183680)> running `nosetests --with-xunitmp --cover-package=forgechat --processes=4 --process-timeout=360` in ForgeChat <DummyProcess(Thread-6, started daemon 140635482879744)> running `nosetests --with-xunitmp --cover-package=forgediscussion --processes=4 --process-timeout=360` in ForgeDiscussion .. ---------------------------------------------------------------------- Ran 2 tests in 2.439s OK finished `nosetests --with-xunitmp --cover-package=forgechat --processes=4 --process-timeout=360` in ForgeChat <DummyProcess(Thread-5, started daemon 140635830183680)> running `nosetests --with-xunitmp --cover-package=forgegit ` in ForgeGit .................. ---------------------------------------------------------------------- Ran 18 tests in 6.811s OK finished `nosetests --with-xunitmp --cover-package=forgeactivity --processes=4 --process-timeout=360` in ForgeActivity <DummyProcess(Thread-3, started daemon 140635846969088)> running `nosetests --with-xunitmp --cover-package=forgeimporters --processes=4 --process-timeout=360` in ForgeImporters ....................................SSS....... ---------------------------------------------------------------------- Ran 46 tests in 13.395s OK (SKIP=3) finished `nosetests --with-xunitmp --cover-package=forgeblog --processes=4 --process-timeout=360` in ForgeBlog <DummyProcess(Thread-4, started daemon 140635838576384)> running `nosetests --with-xunitmp --cover-package=forgelink --processes=4 --process-timeout=360` in ForgeLink ................. ---------------------------------------------------------------------- Ran 17 tests in 6.106s OK finished `nosetests --with-xunitmp --cover-package=forgelink --processes=4 --process-timeout=360` in ForgeLink <DummyProcess(Thread-4, started daemon 140635838576384)> running `nosetests --with-xunitmp --cover-package=forgesvn ` in ForgeSVN ....No config file found, using default configuration . ---------------------------------------------------------------------- Ran 5 tests in 21.449s OK finished `nosetests --with-xunitmp --cover-package=alluratest --processes=4 --process-timeout=360` in AlluraTest <DummyProcess(Thread-2, started daemon 140635855361792)> running `nosetests --with-xunitmp --cover-package=forgeshorturl --processes=4 --process-timeout=360` in ForgeShortUrl ................................................S.....................................................SSSS..SS..........S. ---------------------------------------------------------------------- Ran 122 tests in 18.358s OK (SKIP=8) finished `nosetests --with-xunitmp --cover-package=forgeimporters --processes=4 --process-timeout=360` in ForgeImporters <DummyProcess(Thread-3, started daemon 140635846969088)> running `nosetests --with-xunitmp --cover-package=forgetracker --processes=4 --process-timeout=360` in ForgeTracker ........... ---------------------------------------------------------------------- Ran 11 tests in 4.176s OK finished `nosetests --with-xunitmp --cover-package=forgeshorturl --processes=4 --process-timeout=360` in ForgeShortUrl <DummyProcess(Thread-2, started daemon 140635855361792)> running `nosetests --with-xunitmp --cover-package=forgeuserstats --processes=4 --process-timeout=360` in ForgeUserStats ................................................................. ---------------------------------------------------------------------- Ran 65 tests in 36.697s OK ............ ---------------------------------------------------------------------- Ran 12 tests in 10.422s OK finished `nosetests --with-xunitmp --cover-package=forgediscussion --processes=4 --process-timeout=360` in ForgeDiscussion <DummyProcess(Thread-6, started daemon 140635482879744)> running `nosetests --with-xunitmp --cover-package=forgewiki --processes=4 --process-timeout=360` in ForgeWiki finished `nosetests --with-xunitmp --cover-package=forgeuserstats --processes=4 --process-timeout=360` in ForgeUserStats <DummyProcess(Thread-2, started daemon 140635855361792)> running `npm run lint-es6` in . > [email protected] lint-es6 /x1/jenkins/jenkins-slave/workspace/Allura > eslint -c .eslintrc-es6 --ignore-path .eslintignore-es6 > Allura/allura/public/**/*.es6.js || true sh: 1: eslint: not found finished `npm run lint-es6` in . .........................................................S........ ---------------------------------------------------------------------- Ran 66 tests in 27.490s OK (SKIP=1) finished `nosetests --with-xunitmp --cover-package=forgewiki --processes=4 --process-timeout=360` in ForgeWiki ............................................................................................................................................................................................... ---------------------------------------------------------------------- Ran 191 tests in 71.357s OK finished `nosetests --with-xunitmp --cover-package=forgetracker --processes=4 --process-timeout=360` in ForgeTracker ............................................................................................................................................................................................................................................................................................S..........................................................F...................................................................................................................................................................................................SSSSSSSSSSS..........................................................................................................................................................S................................................................................................................................................................................................................................................................................................................................................................... ====================================================================== FAIL: allura.tests.functional.test_static.TestStatic.test_static_controller ---------------------------------------------------------------------- Traceback (most recent call last): File "/x1/jenkins/jenkins-slave/workspace/Allura/.allura-venv/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/x1/jenkins/jenkins-slave/workspace/Allura/Allura/allura/tests/functional/test_static.py", line 24, in test_static_controller self.app.get('/nf/_static_/wiki/js/browse.js') File "/x1/jenkins/jenkins-slave/workspace/Allura/AlluraTest/alluratest/validation.py", line 302, in get self._validate(resp, 'get', val_params) File "/x1/jenkins/jenkins-slave/workspace/Allura/AlluraTest/alluratest/validation.py", line 281, in _validate validate_js(content) File "/x1/jenkins/jenkins-slave/workspace/Allura/AlluraTest/alluratest/validation.py", line 204, in validate_js report_validation_error('js', fname, stdout) File "/x1/jenkins/jenkins-slave/workspace/Allura/AlluraTest/alluratest/validation.py", line 87, in report_validation_error ok_(False, message) AssertionError: js Validation errors (/tmp/eslint-Rz217n.js): npm ERR! Error: ENOENT, no such file or directory '/x1/jenkins/jenkins-slave/workspace/Allura/node_modules/eslint/package.json' npm ERR! You may report this log at: npm ERR! <http://bugs.debian.org/npm> npm ERR! or use npm ERR! reportbug --attach /x1/jenkins/jenkins-slave/workspace/Allura/Allura/npm-debug.log npm npm ERR! npm ERR! System Linux 3.2.0-101-generic npm ERR! command "node" "/usr/bin/npm" "run" "eslint" "--" "-c" "/x1/jenkins/jenkins-slave/workspace/Allura/Allura/../.eslintrc-es5" "--no-ignore" "/tmp/eslint-Rz217n.js" npm ERR! cwd /x1/jenkins/jenkins-slave/workspace/Allura/Allura npm ERR! node -v v0.6.12 npm ERR! npm -v 1.1.4 npm ERR! path /x1/jenkins/jenkins-slave/workspace/Allura/node_modules/eslint/package.json npm ERR! code ENOENT npm ERR! message ENOENT, no such file or directory '/x1/jenkins/jenkins-slave/workspace/Allura/node_modules/eslint/package.json' npm ERR! errno {} npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /x1/jenkins/jenkins-slave/workspace/Allura/Allura/npm-debug.log npm not ok -------------------- >> begin captured stdout << --------------------- Running setup_app() from allura.websetup --------------------- >> end captured stdout << ---------------------- ---------------------------------------------------------------------- Ran 1060 tests in 140.761s FAILED (SKIP=13, failures=1) finished `nosetests allura/tests/ --with-xunitmp --cover-package=allura --processes=4 --process-timeout=360` in Allura .......................................................................................... ---------------------------------------------------------------------- Ran 90 tests in 122.112s OK finished `nosetests --with-xunitmp --cover-package=forgesvn ` in ForgeSVN ....................................................................................................................................... ---------------------------------------------------------------------- Ran 135 tests in 186.608s OK finished `nosetests --with-xunitmp --cover-package=forgegit ` in ForgeGit Running setup_app() from allura.websetup /p/test/wiki/_discuss/thread/498e7170/ 200 OK {"sidebar": 1, "jinja": 1, "markdown": 4, "ming": 107} Build step 'Execute shell' marked build as failure Recording plot data Skipping Cobertura coverage report as build was not SUCCESS or better ... Recording test results
